Flaky Test Quarantine - CI/CD Glossary Definition
Quarantining a flaky test keeps it running and monitored but stops it from failing the build, protecting merge velocity without simply deleting the test.
Flaky test quarantine moves known-flaky tests into a non-blocking bucket so their intermittent failures do not fail the pipeline, while they are still run and tracked so they can be fixed and returned to the blocking suite.
Quarantine is a controlled middle ground between trusting a flaky test and removing it.
Quarantine, do not forget
A quarantined test should still execute and report so its flake rate is visible; otherwise quarantine becomes a graveyard. Set an expectation to fix or delete it within a bounded time.
Related guides
Flaky Test - CI/CD Glossary DefinitionFlaky Test: A **flaky test** passes and fails on the same code due to nondeterminism (races, timing, external…
Mutation Testing - CI/CD Glossary DefinitionMutation Testing: Mutation testing measures test-suite quality by introducing small changes (mutants) into th…
Retry Budget - CI/CD Glossary DefinitionRetry Budget: A retry budget caps how many automatic retries are allowed over a window, so retrying transient…