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

test(acceptance): qualify preference concurrency and Board membership

Browse Source
This commit is contained in:
cesnimda
2026-10-10 22:39:25 +02:00
parent eba7ad19c6
commit 227e3b4a22
3 changed files with 488 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/redesign/phase-5/p5-15/p5-15-04/README.md
+2 -2
View File
@@ -16,9 +16,9 @@ No API/schema migration, destructive operation, renderer geometry/font/print-rul
## Reliability and capacity investigation
The diagnostic qualification extends the existing native preference scenario to twelve alternating English/Bokmål language and notification writes while four real report/notification reads overlap. It checks actual PUT statuses and owned readback, then reloads. This directly exercises the recorded overlap without mocking persistence or inventing a common cause for two historical failures.
The diagnostic qualification extends the existing native preference scenario to twelve alternating English/Bokmål language and notification writes while four real report/notification reads overlap. All twelve rounds returned language204/notification200, all four reads200 and correct owned readback, with EN/enabled-reminder persistence after reload. This directly exercises the recorded overlap without mocking persistence or inventing a common cause for two historical failures. Historical500 causes are **not reproduced in this finite run**, not repaired or closed. [Actual evidence](evidence/reliability-capacity.json).
The new Board diagnostic creates synthetic owned populations of 200 and 1,000 jobs, verifies the real full-result API, and compares every rendered card ID with its membership. API latency, payload bytes and render timing are observations; there is no approved production performance threshold to declare satisfied. Neither a query cap nor speculative pagination/virtualisation was introduced. The existing full-array O(N) architecture and physical-touch acceptance remain open. These diagnostic additions are not yet executed or claimed passing in this classification checkpoint; the native runner will execute them after its complete ordinary/security lanes. Their completed evidence will be pushed as a separate unit.
The new Board diagnostic created synthetic owned populations of 200 and 1,000 jobs and passed exact real API/DOM ID membership at both sizes. Observations:200jobs/API33ms/render1,040ms/236,253bytes;1,000jobs/API19ms/render1,612ms/1,182,578bytes. These are finite local measurements, with no approved production performance threshold to declare satisfied. Neither a query cap nor speculative pagination/virtualisation was introduced. The existing full-array O(N) architecture and physical-touch acceptance remain open. All three separate diagnostics pass, versus the inherited two; extending preference rounds does not add twelve test cases. The diagnostic/evidence unit is committed/pushed independently.
The [CV save-state investigation](../p5-15-01/INTERMITTENT_FAILURES.md) qualifies the editor's existing 800ms autosave boundary with a controlled test clock: pending draft/focus/no write before it, exact versioned save afterward. No saving implementation changes. The untraced historical incident remains OPEN; passing reruns alone do not establish its original cause.