stabilizing-flaky-tests
Diagnoses and fixes tests that fail intermittently, by root cause (timing, shared state, data collision, environment, order dependence, external dependency, or a real race in the application), proves the fix under the conditions that broke it, and contains what cannot be fixed yet with an owned, expiring quarantine. Use when a test fails randomly or passes on retry, when it passes locally but fails in CI, when a pipeline goes green after a re-run, when a suite needs retries to pass, when a flake list or quarantine keeps growing, or when someone proposes raising a timeout to make a failure go away. Applies even when the request never says flaky. For a test that fails on every run, use diagnosing-test-failures.
Pinned to revision c4efc46815a7, so it is the text this page describes rather than whatever the author pushed since.
Files
- skills/stabilizing-flaky-tests/SKILL.md
- skills/stabilizing-flaky-tests/resources/flake-record-template.md
- skills/stabilizing-flaky-tests/resources/quarantine-policy.md
- skills/stabilizing-flaky-tests/resources/reproduction-recipes.md
- skills/stabilizing-flaky-tests/resources/root-cause-catalogue.md
Every link opens the file at its source, pinned to the revision this page describes.