529851a8fe
Rescue the WorkflowNodeEditor quarantine by waiting for inspector fields before asserting. - make the foreach inspector Mode assertion wait for the panel to finish rendering - wait for the code node Source and Timeout inputs before editing them to avoid the inspector race - remove WorkflowNodeEditor.test.tsx from the dashboard quarantine config and ledger Files changed: .../app/components/__tests__/WorkflowNodeEditor.test.tsx | 6 +++--- packages/dashboard/vitest.config.ts | 4 +--- scripts/lib/test-quarantine.json | 8 +------- 3 files changed, 5 insertions(+), 13 deletions(-) Fusion-Task-Id: FN-6191 Fusion-Task-Lineage: 57fb1dcc-3e50-4ba1-8488-fcff204c1d76
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": []
|
|
}
|