b480699e06
Rescue the dashboard quarantine candidates by restoring stable shared mocks and refreshing quarantine evidence. - Remove QuickEntryBox and chat-routes from the dashboard quarantine config and ledger. - Add iterable chat task document tool mocks across dashboard session test helpers. - Refresh the test velocity baseline and history with zero quarantined tests. Files changed: docs/test-velocity-baseline.md | 20 ++-- .../src/__tests__/session-error-recovery.test.ts | 2 + .../session-persistence-roundtrip.test.ts | 2 + .../src/__tests__/session-reconnect.test.ts | 2 + .../src/__tests__/session-resume-history.test.ts | 2 + packages/dashboard/src/test/mockCoreEngine.ts | 6 ++ packages/dashboard/vitest.config.ts | 13 ++- scripts/lib/test-quarantine.json | 10 -- scripts/test-velocity-history.json | 111 +++++++++++++++++++++ 9 files changed, 144 insertions(+), 24 deletions(-) Fusion-Task-Id: FN-6642 Fusion-Task-Lineage: 76e51d76-ce9a-4e68-9aa0-ad83cdf351a9
6 lines
881 B
JSON
6 lines
881 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": [
|
|
]
|
|
}
|