93b2288d37
Rescue and ratchet non-CLI quarantine state across engine, core, and dashboard suites. - Empty the core, dashboard, and engine quarantine exclude arrays after proving rescued suites run under package load. - Replace broad AI-merge active-session registry cleanup with path-scoped unregistering in engine tests. - Delete the duplicate soft-delete blocker residue suite and clear the quarantine ledger. - Document the non-CLI quarantine sweep pattern for future rescues. Files changed: docs/testing.md | 2 + packages/core/vitest.config.ts | 10 +- packages/dashboard/vitest.config.ts | 12 +- .../merger-ai-cleanup-active-session.test.ts | 20 +++- .../engine/src/__tests__/merger-ai-cleanup.test.ts | 5 +- .../soft-delete-blocker-residue.test.ts | 128 --------------------- packages/engine/vitest.config.ts | 12 +- scripts/lib/test-quarantine.json | 65 +---------- 8 files changed, 40 insertions(+), 214 deletions(-) Fusion-Task-Id: FN-6433 Fusion-Task-Lineage: 18c37475-e6e1-4358-9350-eca65cf53b68
5 lines
884 B
JSON
5 lines
884 B
JSON
{
|
|
"$comment": "Flaky-test quarantine ledger (deletion ratchet \u2014 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 \u2014 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": []
|
|
}
|