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

test(e2e): isolate browser fixtures from provider worker

Browse Source
This commit is contained in:
cesnimda
2026-10-23 03:47:50 +02:00
parent a4cf429fb3
commit b9e052cd22
5 changed files with 848 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/redesign/phase-9/p9-06/DEFECTS.md
+4
View File
@@ -2,6 +2,10 @@
Status is evidence-specific. Historic acceptance records remain unchanged. A passing characterization of a known limitation does not make the limitation safe.
**P9-T03: test isolation failure (High for qualification integrity).** The original browser API fixture inherited `SavedJobSearchAlertsEnabled=true`. Its browser interception could not block server-originated provider traffic. The third shard completed with 87 passes/1 failure: the responsive discovery test's active saved search acquired `lastRunAtUtc=2026-10-23T01:04:07.2042193+00:00` instead of remaining null. The enabled worker starts after 30 seconds and its real NAV search completes before writing that timestamp. This establishes that the original fixture did not provide the intended local-only provider boundary; it is not a product regression or live-provider acceptance. Synthetic accounts/searches were used. No payload/header/token capture or further external investigation was performed.
The browser-only configuration now explicitly disables that existing provider worker, preserving production settings, manual local API contracts and every assertion. The complete third-shard successor passed 88/88 with exit 0, including the original eight-vector preservation assertion. All four ordinary shards and inherited Phase 9 diagnostics rerun under the corrected fixture; earlier successful shards remain superseded, not combined with the corrected run. [Worker isolation delta](../p9-00/worker-isolation-delta.json) retains the exact single-config change and both manifest hashes. Complete final reconciliation remains pending.
| ID | Severity / impact | Reproduction and disposition | Owner / closure | Phase 9 / production |
|---|---|---|---|---|
| P9-T01 | Medium test reliability: parser descendant test could time out before it had a descendant | Entry sidecar 55 pass/1 fail (missing PID); isolated run passes; explicit slow startup reproduces the race. Fixture now waits for its child PID before the unchanged 200 ms deadline. Real process-tree kill and HTTP 504 assertions retained. Focused green and full 56/56 successor. No parser product change. | QA; `.artifacts/phase9/sidecar-entry-failed.*`, `sidecar-fixture-red.*`, `sidecar-fixture-green.*`, `sidecar.xml` | Resolved in tested Windows environment; Linux run remains separate. |