Flaky Test - CI/CD Glossary Definition
A flaky test yields different results on identical code, usually due to nondeterminism or shared state.
A flaky test passes or fails inconsistently on the same code, without any change. Common causes are timing races, ordering dependencies, and reliance on external services.
Flaky tests erode trust in CI: developers start ignoring failures, which lets real regressions slip through. Quarantining and fixing flakes is essential to keep the signal clean.
In CI
Retrying a flaky test can mask the problem. Track flake rates and fix the root cause; self-healing runners can retry mechanical failures but flakes need a code fix.
Related guides
Nondeterministic Test - CI/CD Glossary DefinitionNondeterministic Test: A nondeterministic test produces results that depend on uncontrolled factors like timi…
Test Pollution - CI/CD Glossary DefinitionTest Pollution: Test pollution occurs when one test leaves behind state (files, database rows, global variabl…
Test Isolation - CI/CD Glossary DefinitionTest Isolation: Test isolation means each test runs independently, without depending on or affecting other te…