Files
lmxopcua/docs/ui-consistency/ot04-05/verification.md
T

31 lines
5.1 KiB
Markdown
Raw Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
# OT04–05 navigation and orientation
The six assigned existing files and new NavigationPolicyRenderTests complete the bounded navigation/Home/Namespace compatibility slice. Existing routes, route authorization attributes, C# page parameter declarations and the MainLayout session/footer/body are unchanged (source-guard.json). No endpoint, data-loading, model, configuration, operation or deployment behavior changed.
## Result
- MainLayout enables canonical Theme1.0.1 ScrollNav and groups existing destinations into Operations, Configuration, Scripting, Administration and Secrets. ConfigEditor gates Raw/UNS/Scripts/Deployments; FleetAdmin gates role grants/API keys; the package's own ManagePolicy independently gates Secrets. Read-only routes remain available, including certificates, reservations and script log. Gates use exact destination policies, not inferred role strings.
- Home supplies a useful Fleet status action and existing host/cluster orientation, with authoring/deployment links only for ConfigEditor. It adds no aggregate data, environment guess or status metric.
- ClusterNav removes the ordinary retired Namespace destination and adds aria-current for its four existing readable destinations. Namespace list/new/edit URLs remain; both compatibility pages now have h1 and product title, plus real Raw/UNS links only for ConfigEditor.
- SecretsNavLinkTests identifies the Secrets-specific policy wrapper rather than assuming the first AuthorizeView. Its source-root lookup now starts at the compiled test's CallerFilePath, supporting isolated artifacts without changing assertions. Stale remarks claiming no bUnit were corrected.
## Verification
Meaningful root-authored NavigationPolicyRenderTests baseline: 3 failures/1 pass, retained evidence/red.log. Added Home/compatibility role cases and an independent Secrets-policy case. The first isolated-artifacts run exposed the old sourceguard's testbinary ancestry assumption (3 source-root failures/8 passes); fixed source lookup, retained raw evidence. No bypass, skip or removed assertion.
```sh
dotnet test tests/Server/ZB.MOM.WW.OtOpcUa.AdminUI.Tests/ZB.MOM.WW.OtOpcUa.AdminUI.Tests.csproj --artifacts-path /tmp/ot04-05-artifacts --filter 'FullyQualifiedName~NavigationPolicyRenderTests|FullyQualifiedName~SecretsNavLinkTests|FullyQualifiedName~PageAuthorizationGuardTests|FullyQualifiedName~DeleteConfirmRenderTests'
```
**18/18 pass, zero skips**, including original delete confirmation tests. No new build warnings in this checkpoint. Full suite belongs to the coordinated integration freeze; this report does not claim it ran here.
`canary/` is a separate, source-referencing Razor host with its own route assembly, synthetic authenticated principals and the real role-policy mapping. It registers no operational/data providers. Actual application route attributes remain protected by the independent reflection guards; fixture deep-link rendering is markup validation, not an authentication endpoint test. The fixture maps only its explicit Home/three compatibility routes and read-only provenance endpoint; no real service action endpoint exists.
**12 actual Chromium scenes/288 assertions**: Viewer, Operator, Designer and Administrator at 1440px, 390px, and real 200% browser zoom (720px layout viewport/DPR2). Each verifies one h1, product-qualified title, first useful Fleet action before opening navigation, exact policy link presence/absence, retained readable links, current Overview location, reachable session footer, breakpoint-appropriate scrolling, no horizontal overflow, all three retained compatibility routes with gated links and no retired ordinary tab, no page errors. `browser-results.json`, twelve screenshots and `browser.py` retain proof. The script imports ignitionoee's existing loopback-only real browser zoom helper; this explicit harness dependency does not affect production.
The first browser run incorrectly expected independent ScrollNav scrolling on phones. Canonical layout intentionally uses page scrolling below 992px; corrected the assertion to match the documented shared behavior, retaining the initial log. No theme override or local CSS workaround was introduced. No state persistence/business operations were exercised.
## Scope and limitations
The old Namespace pages continue to describe their compatibility purpose; no retired editor behavior was reinstated. Policy checks affect discoverability only and preserve endpoint/route security. Cluster overview action links are a different agent's tested slice. This checkpoint does not claim operational fleet data, live roles against an identity provider, or a deployed host acceptance. Parent review accepted the separate Secrets section as a taxonomy refinement of the planned four groups: it remains independently governed by the package policy rather than nested under FleetAdmin. Final copy/heading corrections use canonical page-head/h2.panel-head and concise compatibility wording. A narrow final render passed all six Home/list/edit scenes at1440/390 after these markup-only corrections (final-render.json), checking h1/page-head/h2.panel-head and final compatibility copy. Fixture shutdown and exact scoped commit follow parent review. No ledger/gate edits.