Skip to main content
Testing12 min read

Eliminating Flaky Tests: A Systematic Approach

How I took a test suite from 10% flaky rate to under 1% — retry logic, test isolation, deterministic data, and the patterns that make tests reliable.

By Jason TeixeiraFebruary 28, 2026
TestingQAFlaky TestspytestCI/CDSelenium
Share:
On this page

A flaky test is a test that sometimes passes and sometimes fails without any code changes. At 10% flaky rate, developers stop trusting the test suite. At 20%, they stop running it.

I've taken suites from 10% flaky to under 1%. Here's the systematic approach.

Step 1: Measure the Flake Rate

You can't fix what you don't measure. Track flakiness over time:

\

Reader route

article -> proof -> offer

ReadClusterProofScope

cluster

Testing & QA

intent

Testing

route

next step

What to do with this

Turn the note into a build path.

If this topic maps to a real business problem, keep reading the cluster, study the academy path, or route the work into a scoped engagement.

Jason Teixeira
Written by
Jason Teixeira
Founder, Sage Ideas Studio · Principal Engineer
livebuild a1556e22026-06-19 03:29Z
// solo studio// no analytics resold// every commit human-reviewed