Description
With ~90 test files already in __tests__/ plus E2E and accessibility suites, some tests are statistically likely to be intermittently flaky (especially anything touching timers, animations, or polling — several components mentioned in the codebase use setInterval/polling patterns). There's no process for identifying or quarantining flaky tests, which erodes trust in CI over time.
Requirements and context
- Add a CI job that runs the full suite 3× on a schedule (not per-PR, to avoid tripling CI cost) and reports tests with inconsistent pass/fail results
- Document a quarantine process (
.skip with a linked tracking issue) in CONTRIBUTING.md
- Do an initial pass identifying any currently-known-flaky tests
Suggested execution
git checkout -b ci/add-flaky-test-detection
- Add scheduled multi-run CI job
- Document quarantine process
- Do initial flaky-test triage pass
Example commit message
ci: add flaky test detection and quarantine process
Description
With ~90 test files already in
__tests__/plus E2E and accessibility suites, some tests are statistically likely to be intermittently flaky (especially anything touching timers, animations, or polling — several components mentioned in the codebase usesetInterval/polling patterns). There's no process for identifying or quarantining flaky tests, which erodes trust in CI over time.Requirements and context
.skipwith a linked tracking issue) inCONTRIBUTING.mdSuggested execution
Example commit message
ci: add flaky test detection and quarantine process