Flakiness and Maintenance for Quality Assurance (QA)s
Flakiness is when a test passes and fails on the same code without any change. Maintenance covers finding the cause, such as timing, shared data or environment issues, then fixing it and keeping the suite fast through parallel runs and clear reports so the team keeps trusting results.
Stage: Test Automation · Part of the Quality Assurance (QA) roadmap · Last reviewed 19 November 2026
What to learn in Flakiness and Maintenance
- Reproduce a flaky test by rerunning it in a loop
- Separate test, application and environment causes of intermittent failures
- Remove shared state so tests can run in any order
- Replace race-prone waits with condition-based waits
- Run tests in parallel and make data unique per worker
- Read a report with traces and screenshots to diagnose a failure
Flakiness and Maintenance interview questions
How do you handle a flaky test?
Reproduce it, read the trace or logs, and find the cause: timing, shared data, order dependence or a real race in the app. Fix that cause. Quarantine it with a tracking ticket only briefly, and do not hide it behind blind retries.
What must be true before tests can run in parallel?
Tests must be independent: no reliance on order, no shared mutable data, and unique accounts or records per worker. Each test should create and clean up its own state, or use isolated contexts, otherwise parallel runs cause random failures.
Where Flakiness and Maintenance fits in the Quality Assurance (QA) roadmap
Flakiness and Maintenance belongs to the Test Automation stage (beginner level), which takes about 9 hours. Reliable, maintainable checks.
Other units in this stage
Back to the full Quality Assurance (QA) roadmap