Testing in a Continuous Delivery World
summary
Claim: flipping to continuous deployment forces practices like TDD and makes teams actually write tests instead of promising them, with some teams enforcing 100% coverage as a gate. Delivery pipelines run fast enough to deploy 30 times a day, enabling cheap experiments and canceling multiweek features after days of results. Operations and testing merge—use monitoring (Nagios-style), canary releases, and feature toggles as continuous tests. Expect infrastructure as code testing with Chef/Puppet and a shift from UI end-to-end reliance to targeted component and protocol tests.
AI-written summary · about
chapters (7)
- 0:00Start
- 5:48Why I Really Like Continuous Delivery
- 13:41Exploratory Testing
- 30:10Infrastructure Tests
- 33:16Hypothesis Driven Development
- 35:52Landing Pages
- 38:40Testing Strategy
related talks
34mWhy continuous testing is essential
49mThe Whole Team Approach to Testing in Continuous Delivery
41mShift Left, Shift Right and Improve the Centre
24mOrchestrating automation tests for Continuous testing
28mClimbing the Mountain of CI/CD: A Tester’s Tale
44mContinuous Performance Testing in DevOps
47mHow Testing is Evolving in DevOps
32mBetter Continuous Testing in DevOps