TEST-AUTOMATION5 MIN READ
Stabilize a Flaky Test With PDSA
Use PDSA decisions to turn a flaky test into a trustworthy signal or remove it.
The signal problem Checkout smoke fails 9 percent of CI runs. The team reruns until green, so the gate blocks time but not bad releases. A flaky test costs twice: it slows the team and teaches people to distrust automation. PDSA for flake work Prediction -> small change -> study -> act Each decision below protects one idea: test one failure theory at a time, then decide based on the signal. Reflex Add retries and move on The team learns whether the test can become a release signal. A flaky test is a hypothesis problem before it is a tooling…
Read the full lesson
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in