Apply the dashboard quarantine deletion ratchet by removing stale quarantined suites and clearing the active skip ledger. - Delete dashboard component and API test files that remained quarantined under the ratchet. - Empty the dashboard Vitest quarantine exclude list so future quarantines must be newly mirrored. - Clear the quarantine ledger entries after deleting their associated files. Files changed: ...hatView.regular-composer-no-right-line.test.tsx | 108 - .../components/__tests__/MissionManager.test.tsx | 5654 ------------------ .../app/components/__tests__/ModalReentry.test.tsx | 439 -- .../components/__tests__/ModelSelectorTab.test.tsx | 1325 ----- .../components/__tests__/NewAgentDialog.test.tsx | 2043 ------- .../__tests__/OAuthReloginBanner.test.tsx | 237 - .../__tests__/PlanningModeModal.favorites.test.tsx | 540 -- .../__tests__/PlanningModeModal.questions.test.tsx | 1230 ---- .../PlanningModeModal.swipe-back.test.tsx | 239 - .../components/__tests__/SkillsView.css.test.ts | 89 - .../app/components/__tests__/mobile-css.test.tsx | 143 - .../dashboard/src/__tests__/mission-e2e.test.ts | 6176 -------------------- packages/dashboard/src/__tests__/planning.test.ts | 3633 ------------ packages/dashboard/vitest.config.ts | 40 +- scripts/lib/test-quarantine.json | 70 +- 15 files changed, 8 insertions(+), 21958 deletions(-) Fusion-Task-Id: FN-6454 Fusion-Task-Lineage: f18e940d-f8ee-4ade-aedb-714b8e39e2a4
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": []
|
|
}
|