The Build That Cried Broken: Building Trust in Your Continuous Integration Tests
summary
Team inherits 4,000 flaky UI tests and builds a disciplined plan: create a stable CI pipeline separate from unstable and bug pipelines, log every test run to a small database with a UI for prioritized triage, assign weekly "build duty" to triage failures, and enforce techniques like Ajax counter waits, stable identifiers and web‑service shortcuts. Result: unstable tests stay under 1.5%, the trusted pipeline stays green and developers act on real failures.
AI-written summary · about
chapters (10)
- 0:00Intro
- 2:54THE SHEPHERD BOY AND THE WOLF
- 5:22THE FOX AND THE GOAT
- 7:13THE LIONESS AND THE VIXEN
- 9:52Manage Flaky Tests
- 16:25THE ASTROLOGER
- 21:38Monitor Builds
- 23:48THE FARMER AND THE STORK
- 31:49THE DOG AND THE HARE
- 33:32How the Story Ends...
related talks
31mThe Build That Cried Broken: Building Trust in Your Continuous Integration Tests
32mBuilding Confidence Together: Continuous Integration & Testing
38mScaling Automated Testing & Architecture from Startup to Enterprise
46mFlaky, Fragile, and Forgotten: The Fall of a Test Automation Project
01h 15mThe Practices That Make Continuous Integration
20mThe Road to Continuous Testing
39mBuilding The Blocks of Trust In Automation
28mOrganizational Stability through Reliable Software through Testing