How to defuse a bomb Wait, I mean a bug
summary
Two-week cycles run with a 700-case regression suite and twelve manual testers; testing moves left onto individual branches and into paired sessions so bugs get caught before merge. A mirrored pre-production environment reduces flaky false positives. Test ops owns releases, session-based testing uses 15-minute charters and a 30–120 minute window, daily five-minute bug triage prioritizes issues, and biweekly bug scrubs gather 12 QA people. Selenium automation grows into a large suite and dedicated automation engineers cut manual time by about five to six hours weekly.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 2:15Key Takeaways
- 7:10Pair Testing
- 9:38What would you test
- 16:05Sessionbased testing
- 16:55How to do an SBT
- 21:01Bug triage
- 24:23Bug scrub
- 27:04QA support
- 32:30Automation strategy
related talks
36mHow programmers & testers can be productive
10mBeyond “try harder”: Effective strategies to tackle bugs
42mBeyond “Just Try Harder”- Three effective strategies to tackle bugs
53mTransforming testing methodologies: From manual to robust strategies
41mShift Left, Shift Right and Improve the Centre
31m#testedAF: Test All the Things (Not Just Your Units)
26mThe Impact of Testing on a DevOps Pipeline
45mImproved Regression Testing in Agile