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

docs(qa): qualify Phase 9 regression and acceptance

Browse Source
This commit is contained in:
cesnimda
2026-10-23 07:31:27 +02:00
parent 0fb108bd67
commit 8e7e3f6387
63 changed files with 64728 additions and 6835 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/redesign/phase-9/p9-01/README.md
+2 -2
View File
@@ -1,6 +1,6 @@
# P9-01 connected functional journeys
Execution outcomes are recorded in [ordinary-cases.json](ordinary-cases.json) and [validation](../validation.json); a named test file below describes its actual scope, not an extra pass count. Final full-suite completion is required. No route-only screenshot is treated as a successful mutation journey.
The final ordinary suite completed **362/362 passed** across four serial native shards (98 + 87 + 88 + 89), with zero failures, skips, flaky results, retries or run-level errors. Exact unique case IDs equal full native discovery. [ordinary-cases.json](ordinary-cases.json) and [validation](../validation.json) retain actual single passed results and process exits. A named test file below describes scope, not an extra pass count. Route screenshots do not establish successful mutation journeys.
| Journey | Existing exercised sequence / evidence owner | Qualification retained |
|---|---|---|
@@ -16,4 +16,4 @@ Execution outcomes are recorded in [ordinary-cases.json](ordinary-cases.json) an
All33 concrete routes are additionally tied to explicit applied-state/read/overflow samples in [QA_MATRIX](../QA_MATRIX.md). The native route census tests ordinary-role/admin/anonymous ownership posture separately from the privileged synthetic screenshot fixture. Admin page rendering is not an authorisation grant. All service/API/sidecar results are distinguished in [P9-04](../p9-04/README.md), [P9-05](../p9-05/README.md) and final regression.
Failure cases deliberately intercept a specific local read/write or transport response; successful saves and ownership checks use local native API where stated by their fixtures. No new integration or external provider call was introduced. The exact per-case titles and raw attachments are retained so reviewers can distinguish intercepted UI recovery from persisted API evidence.
Failure cases deliberately intercept a specific local read/write or transport response; successful saves and ownership checks use local native API where stated by their fixtures. P9-T03 exposed a gap in the original test boundary: the existing server worker could run a real NAV search despite browser interception. The corrected browser configuration disables that worker and the complete successor reruns under it. No live-provider acceptance is inferred from the earlier traffic. Exact case titles and attachments distinguish intercepted UI recovery from persisted API evidence.