Taking Control Of Your Test Environment
summary
Shows concrete moves to stop flaky environments: add automation to catch regressions, quarantine flaky checks into a separate bug suite, use feature branches so master stays green, and make flaky failures reproducible (run the failing check on multiple threads). Replaces flaky third parties with stubs or captures traffic and run 100 requests in Charles to prove 30% failure. Advocates pairing with ops, asking for incremental access (code, DB, monitoring, deployment), and measuring whether each change actually keeps the build green.
AI-written summary · about
chapters (11)
- 0:00Introduction to the quest
- 1:00The cast of characters
- 5:07Overcoming obstacles
- 10:04Managing build failures
- 15:19Dealing with flaky tests
- 20:14Handling third-party issues
- 25:21Solving communication gaps
- 30:56Unlocking operations knowledge
- 33:23Gaining keys to the castle
- 39:22Closing and acknowledgments
- 41:26Q&A session
related talks
36mFixing Flaky Tests Like a Detective
46mThe state of the Art in Tackling Flaky Tests
28mThe State of Art in Tackling Flaky Tests
46mFlaky, Fragile, and Forgotten: The Fall of a Test Automation Project
40mFinding Flakiness: The Real Reasons Your Tests Aren't Reliable
31mThe Build That Cried Broken: Building Trust in Your Continuous Integration Tests
29mCommon Mistakes that make test cases flaky and how to avoid them
42mDon't Let Your Tests Flake Out