2ecf78af28
Rescue dashboard process lifecycle coverage and clear stale quarantine state. - Track dev server lifecycle work so stale probes and output parsing cannot race cleanup. - Assert duplicate URL detection suppression and fallback probe cleanup across failure, restart, stop, and cleanup paths. - Remove rescued dashboard tests from quarantine config and ledger, and document the loaded-shard proof. Files changed: docs/testing.md | 4 ++ .../src/__tests__/dev-server-process.test.ts | 28 +++++++- packages/dashboard/src/dev-server-process.ts | 74 +++++++++++++++++----- packages/dashboard/vitest.config.ts | 5 +- scripts/lib/test-quarantine.json | 13 +--- 5 files changed, 95 insertions(+), 29 deletions(-) Fusion-Task-Id: FN-6860 Fusion-Task-Lineage: abd22a00-e08e-4f65-bebc-c663c715b40e
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": []
|
|
}
|