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

test(cv-qa): prove connection-loss rollback and bounded parser safety

Browse Source
This commit is contained in:
cesnimda
2026-10-27 05:15:28 +01:00
parent e416420e79
commit 69f189fb2e
4 changed files with 150 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/cv-integration-qa/MARIA_DB_AND_RD21.md
+6
View File
@@ -12,4 +12,10 @@ The run status is now an EF concurrency token, with matching snapshot metadata a
The GREEN cases confirm no canonical write after discard, no discard after apply, retained applied receipts and exact replay after retention, terminal cancellation preservation and rejected terminal retries. Existing owner/tenant and first/existing-profile revision tests remain enabled. A displayed success still requires confirmed durable application.
## Final actual connection-loss qualification
The final current-source lane passes **80/80**, zero skips (`mariadb-final-01/mariadb.trx`); startup, locked restore, test and owned-container cleanup exit0. The additional test terminates only its own active connection's numeric `ServerThread` in the guarded disposable database, after all writes but before outer commit. A returned success or a hung request cannot qualify: it requires a real failure, rejects timeout, checks revision0/pending review/no receipt/no skill or history/unchanged Identity pointer, then verifies exact retry and replay produce one durable revision and one skill. This is actual MariaDB session loss, not a mocked provider exception or a whole-server/power-loss experiment. No production connection is used.
The extra test is a separately bound test-only addition after the full application freeze; all original source hashes remain unchanged. The final provider run includes the seven lifecycle cases and all earlier mapping/rollback/owner/revision cases. A separate warmed sample reports **51.055ms** for reviewed application including validation, merge, transaction and Identity projection; it is not a latency SLA.
This qualifies the exercised disposable MariaDB behavior. It does not establish hosted CI, production database behavior, power-loss recovery or server filesystem/backup integrity. Historical RD21 evidence is preserved; current-source focused races complement rather than replace its full regression lanes.