Flaky Tests & Reliability
Test retry
Also known as: retries, auto-retry
A test retry automatically re-runs a failed test a set number of times and passes it if any attempt succeeds — a way to absorb flakiness so it doesn’t fail the build.
Retries are a coping mechanism, not a cure. They keep pipelines green by hiding intermittent failures, which is useful for velocity — but a test that only passes on the second try is still flaky, and retries mask that signal. Used carelessly, they let genuine intermittent bugs (real race conditions in your product) slip through.
The pragmatic stance: allow limited retries to stay unblocked, but record which tests needed a retry and how often, so flakiness stays visible and gets fixed at the root. Retry counts are themselves a flakiness signal.
- Re-runs a failed test; passes if any attempt succeeds.
- Hides flakiness to keep builds green — but can also hide real intermittent bugs.
- Track retry frequency: it is a measurable flakiness signal, not a fix.
Learn more
Related terms
See it in your own test results
Qualflare detects flaky tests, clusters failures by root cause, and scores release risk from the test results you already produce in CI. Start free.
Start free with Qualflare← Back to the testing & observability glossary.
Last reviewed June 11, 2026