8dc9973997
Remove the orphaned session-cross-tab quarantine ledger entry after confirming the test remains active and rescued. - Document FN-6937's rescue proof and ledger/config lockstep expectation in testing guidance. - Keep the dashboard Vitest quarantine list empty with a note explaining the stale ledger-only cleanup. - Remove the session-cross-tab row from the flaky-test quarantine ledger. Files changed: docs/testing.md | 8 ++++++-- packages/dashboard/vitest.config.ts | 3 +++ scripts/lib/test-quarantine.json | 8 +------- 3 files changed, 10 insertions(+), 9 deletions(-) Fusion-Task-Id: FN-6937 Fusion-Task-Lineage: 34a67bf3-2a7f-49ea-93ab-68fadc81f893
5 lines
878 B
JSON
5 lines
878 B
JSON
{
|
|
"$comment": "Flaky-test quarantine ledger (deletion ratchet — see AGENTS.md 'Flaky tests: quarantine on sight' and docs/testing.md 'Quarantine ledger and the deletion ratchet'). A test observed failing without a corresponding real bug is quarantined ON SIGHT: add an entry here AND a matching one-line `exclude` entry in that package's vitest config, in the same commit. Every entry needs a non-empty `reason` (link the failing run) and a `quarantinedAt` date — the entry expires 14 days later, at which point the test file is DELETED unless someone rescues it with evidence it catches real regressions plus a root-cause fix (never appeasement). There is deliberately no loader module and no automation around this file: it is a dated record, the vitest config exclude is the mechanism, and the sweep is policy executed by whoever touches the suite.",
|
|
"entries": []
|
|
}
|