sorokin.oleg.edu/ARCADIA-Studio
1
0
Fork 0
Code Issues 37 Pull Requests 2 Packages Projects Releases 9 Wiki Activity

test: establish independent inspection before preferred-view creation

Browse Source
This commit is contained in:
Codex-ytr83r
2026-09-25 00:26:42 -07:00
parent 3a7221b80c
commit 6520a89dc0
4 changed files with 36 additions and 15 deletions
Download Patch File Download Diff File Expand all files Collapse all files
harness/projection-navigation-20260925.md
+26 -1
View File
@@ -57,6 +57,31 @@ The desktop attempt at `603a59c` was deliberately interrupted before test execut
Published-preview executable SHA256 `2c03bd6cc3f1110c219e4f57ab94874a121590f83779239a93289b7170664399` reproduces edge selection changing SA to OA, and Architecture switching refused with `diagram_layer`. The isolated valid fixture remained byte-for-byte unchanged after the trial. An earlier fixture used reserved alias `capability` and was rejected; it was corrected before either reproduction. Initial native-dialog capture/input failures also remain separate from application acceptance. Independent evidence review confirmed the resulting screenshot states and persisted byte equality; screenshots alone do not capture the complete action sequence or transient state history.
Candidate Windows GUI save/history/reopen, HTTP regression, broader affected suites and actual rendering acceptance remain outstanding. Raw local evidence is not yet a peer-consumable handoff; publish the consolidated evidence before integration.
The frozen full-workspace attempt at `3a7221b80cfa7924921b3b77f2dd35550247f595`
closed with unchanged tracked inputs and Cargo exit101: core/CLI groups passed616
with1 existing ignore; desktop passed1538, failed1 and retained7 existing ignores.
The sole failure was the new preferred-view test's setup, before child creation:
`Message::Projection` edits and selects the diagram, so the test's expectation
that the parent remained selected was false. An exact isolated rerun and source
review confirmed this. The correction initializes the projection in the fixture,
then uses explicit parent selection and the ordinary diagram picker to establish
independent semantic inspection. Production navigation is unchanged. All other
new canvas tests passed, including Properties, explicit navigation, relationship
Apply/history, child/root semantic layer, and projection/source/history checks.
The command remains a failed workspace run; server tests and doctests were not
reached. Its planned Clippy/build stages were consequently not launched.
The same source's formatting check found one multiline icon call requiring a
single line. The follow-up applies that formatting correction and adds in-app
help describing preserved cross-layer content and contextual inspection. Those
are the only production-file changes after the full suite; the remaining change
corrects the test setup. Follow-up canvas/server/doctest, formatting, strict
Clippy and native-build results must be recorded separately, with their exact
source pin. Reuse successful unchanged core/desktop evidence within these limits;
do not turn the failed workspace command into a pass.
Candidate Windows GUI save/history/reopen, HTTP regression, the corrected test
and final checks remain outstanding. Raw local evidence is not yet a
peer-consumable handoff; publish the consolidated evidence before integration.
Scope boundary: contextual relationship forms retain the canvas while opening; successful Apply retains the existing explicit post-review navigation. The generic child-creation handler is tested for containment and allocation, but the separate architecture palette/performer workflow still offers creation kinds for the diagram layer. Thus an OA performer displayed in an SA Traceability view has no Add activity menu entry; this inherited limitation is not claimed repaired here.