The Whole Team Approach to Testing in Continuous Delivery
summary
Team moves a single-page app to the cloud with a blue/green deploy and a 25–30 developer squad that initially has only two testers and thousands of flaky UI checks. The manual release checklist is discarded, developers pair and learn exploratory testing, automated suites get reorganized using a test suite canvas and UI tests refactored with the page object model. Observability with Mixpanel/Splunk/Datadog, feature toggles, mob testing and a build monitor reduce production regressions and enable reliable twice‑weekly deploys.
AI-written summary · about
chapters (20)
- 0:00Introduction and speaker background
- 3:23Commitment to quality in delivery
- 7:59Turning around testing struggles
- 10:08Visualizing the pipeline
- 12:44Automated regression testing challenges
- 17:19Analyzing test suites for improvement
- 19:30Prioritizing automated test coverage
- 21:35Introduction to observability
- 23:41Testing features for customer value
- 26:32Sustainable pace and team diversity
- 27:57Testers as quality advocates
- 30:04Small teams and impact mapping
- 31:51Mob programming for acceptance testing
- 33:34Building cross-team relationships
- 34:59Psychological safety and leadership
- 36:26Investing in quality speeds delivery
- 37:30Continuous testing in DevOps
- 42:32Breaking down testing silos
- 46:24Challenges and small experiments
- 48:12Closing and Q&A
related talks
42mTesting in a Continuous Delivery World
41mShift Left, Shift Right and Improve the Centre
28mClimbing the Mountain of CI/CD: A Tester’s Tale
53mTransforming testing methodologies: From manual to robust strategies
37mTesting Games
24mAdapting Test Strategies to Modern Deployment Methods
01h 09mScaling up with Embedded Testing
32mClimbing the Mountain of CI/CD: A Tester’s Tale