6 posts tagged with “Pipeline Stability”
How to reduce flaky tests by changing how the team works first: branch length, a written rerun policy, named owners, and the merge bar. Tooling comes after.
Flaky tests in CI/CD cost more than reruns: the pipeline gates a shared trunk and runs on trust. Why the cost scales with team size, and where flakes surface.
CI pipeline stability is a classification, not a pass rate. The three signals that sort every test into healthy, flaky, or broken, and the thresholds to use.
Flaky test detection at scale is reading verdict history, not rerunning everything. The strategies, the flip-rate signal, and classifying healthy, flaky, broken.
How to fix flaky tests: six root-cause classes, the diagnostic checklist per class, and the test-strategy fix most teams skip. Telltale log signatures for each.
The real cost of flaky tests is compute reruns plus developer wait time. The maths on why every flake pays twice, what we observed, and where to start.