pimhwang/ILSpy - ILSpy - git.quantfans.net

Author	SHA1	Message	Date
Siegfried Pammer	ab5fa461af	Retarget assembly tree tests to SharpTreeView; close interaction gaps The assembly/analyzer panes now host SharpTreeView, but ~20 headless tests still queried the old ProDataGrid surface (DataGrid/DataGridRow/Hierarchical Model/HierarchicalNode), so they could not exercise the live tree. Retarget them to SharpTreeView/SharpTreeViewItem and the flattener (ItemsSource) the control actually exposes, and centralise the row/selection lookups in TreeNodeAssertions so the scroll assertions ride the new container type. Driving the retargeted tests against the real control surfaced four genuine gaps, fixed here in SharpTreeView: - Ctrl+A selected nothing on the first press because the base ListBox only selects all once an item inside it is focused; handle it explicitly and make the control itself focusable so the gesture works the moment the pane gains focus. - Left/Right navigation focused the parent/first-child container but never moved the selection (selection must follow the caret); add SelectAndFocus. - The expander toggle had no stable name; name it PART_Expander so hit-target assertions can find it, and align the test to the shipped 13px column (kept at 13 so the +/- box centres on the connector lines). - Tree rows stretch to content width with horizontal scroll, so a row centre can sit past the viewport's right edge; the pointer tests now click within the visible grid width instead of the off-screen row centre. The UseNestedNamespaceNodes re-bind test asserted a ProDataGrid Hierarchical Model swap that no longer exists; rewrite it to assert the live flattener reshapes the visible rows in place when the setting toggles.	4 weeks ago
Siegfried Pammer	f466b2399b	Add per-step visual breakpoints to the headless UI tests To audit what each UI test actually exercises, every step now snapshots the live window to <TestFixtureName>/<TestName>_<NN>_<ShortDescription>.png: a booted frame (emitted automatically by TestHarness.BootAsync), one after each state-changing action, and one before each assertion. Flip ILSPY_TESTS_VISIBLE=1 to render the filmstrip; it lands under %TEMP%/ilspy-test-captures (overridable via ILSPY_TEST_CAPTURES). The step number and fixture/test name are derived automatically so inserting a breakpoint never renumbers the rest. The identity is recorded up front from the real ITest in an ITestAction hook rather than read live: NUnit's TestContext.CurrentContext does not flow onto async continuations, so a capture after an await would otherwise collide under the ad-hoc context. And when rendering is off the whole call is a true no-op -- not even a dispatcher pump -- so instrumenting a test can never perturb the navigation/tab timing it asserts on. Full headless suite stays green.	4 weeks ago
Siegfried Pammer	56afcf8abd	Factor repeated headless-test setup into shared helpers Nearly every headless UI test opened with the same four-line prologue (resolve the shared MainWindow, show it, cast its DataContext, wait for the assembly list), then repeated the corelib lookup, the EnsureLazyChildren + Children.OfType<T>().Single() drill, the registry single-by-header lookups, and the open-an-assembly-and-wait dance. The duplication made the intent of each test hard to see and every signature tweak a suite-wide edit. Collapse those into TestHarness (BootAsync, OpenAssemblyAsync, GetCommand, GetEntry) and TreeNavigation extensions (FindCoreLib, GetChild<T>, Expand<T>), then apply them across the suite. Net ~865 lines of boilerplate removed with no change in behaviour; the full headless suite stays green.	4 weeks ago
Siegfried Pammer	2f6536d8ae	Tree-view options reach the assembly tree Wires the four Display Settings "Tree view options" through to the rendered tree: Assisted-by: Claude:claude-opus-4-7:Claude Code	4 weeks ago