cesnimda/jobtrackingapp
1
0
Fork 0
Code Issues Pull Requests Actions 4 Packages Projects Releases Wiki Activity

test(ui): qualify account sections and editor hierarchy

Browse Source
This commit is contained in:
cesnimda
2026-11-04 01:41:02 +01:00
parent b6d830f279
commit 368e90d572
350 changed files with 6364 additions and 19 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/ui-modernisation/visual-correction/ACCOUNT_EDITOR.md
+7 -1
View File
@@ -10,4 +10,10 @@ PASSED:81 selected account/provider/security/export/catalogue tests/eight suites
Initial phone pilots passed seven account states (before final Identity copy) and six editor states including role-title visual hierarchy. Required final runs on the settled export: **36 configurations /252 account scans** (focused details/connections/security, summary, cancelled session confirmation, cancelled data confirmation with fixture403 export, mail connections), plus **36 /216 application scans** to qualify the changed role heading. No production account, actual deletion/revocation/export, provider activation or model is permitted by these fixtures. Skipped admin/processing checks explicitly remain NOT RUN in account-only mode.
Current status: final browser matrices pending. Use A3_ACCOUNT_FLAT=1 with verify-a3-account-admin.mjs, and A3_VISUAL_MATRIX=1 / A3_FLAT_WORKSPACE=1 with verify-a3-applications.mjs. The existing sources/prototypes do not need another concept-selection decision. Keep source/export identities stable during runs; record actual reports, manually inspect lower focused account sections at phone/tablet/desktop, then seal/publish evidence. Do not declare full34-route/57-group, security/release or owner visual acceptance from these scoped checks.
PASSED on settled source `b6d830f27951271ac2d1acb8855adc43b77cbec0`:36 configurations /252 account accessibility scans and captures, plus36 /216 application scans and captures. Account journeys preserve an unsaved display-name draft across section jumps; cancel session and data confirmations; exercise one fixture403 export each. Application journeys retain36 synthetic status updates,36 visible keyboard-focus checks and three canonical alias checks. These runs supersede overlapping earlier captures rather than adding to them.
Capture correction: the first account run composed scrolled desktop full-page screenshots with fixed navigation in misleading positions. Retained `BROWSER-CAPTURE-FAILURE.json` and one named failure screenshot document the issue. The corrected full252-state run captures focused sections as viewports and top-of-page desktop states as full pages. A corrected1440px focused details capture was visually inspected: navigation remains at the viewport top, fields span useful columns and the purple section outline denotes keyboard focus. Phone security and earlier editor captures were inspected separately. Automated scans do not establish owner visual acceptance.
Limitations: account-only mode does not execute admin/processing scenarios. The fixture deliberately rejects shared companies reads (`/api/companies`,108 recorded unavailable reads) and external Google Fonts; those are not qualified integrations. No real account export, revocation, deletion, provider, model or security/release acceptance. Account and application reports have no browser errors, unexpected writes or accessibility violations. `ACCOUNT_EDITOR_SOURCE_MANIFEST.json` binds runtime sources to the immutable commit, verifier scripts and evidence to the receipt commit, and80 raw export files to the export tested before public-auth development is built.
Next: qualify the public sign-in/recovery language controls and remaining rendered route families. Keep full34-route/57-group, human/device/native-language and final owner visual acceptance OPEN.