Organizational Stability through Reliable Software through Testing
summary
Argues that reliable testing is the foundation of organizational stability, with concrete practices: unit E2E integration and smoke tests, CI/CD pipelines that run validations at commit time, UAT treated as a first-class stage, and rollouts like blue/green or canary. Recommends a multi-stage pipeline with early validations so expensive checks run less often, and measures progress with DORA-style metrics, notably time to restore service under an hour and tracking change‑failure rate.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:56Organizational stability defined
- 3:21Why stability matters
- 8:40Software stability ties to org stability
- 13:18Developers' role in reliability
- 15:22Managers' role in reliability
- 16:47Automated processes beyond testing
- 19:57Optimizing deployment pipeline
- 22:24Measuring stability with DORA
- 24:31Improving dev experience with audits
- 25:16Closing & Q&A
related talks
34mBalancing Early Testing with Real-World Reliability
01h 02mThe Art & Joy of Testing in Production
40mThe Build That Cried Broken: Building Trust in Your Continuous Integration Tests
32mI Test In Production
15mImprove continuous delivery by target quality aspects by your tests
34mWhy continuous testing is essential
22mTest Automation and Beyond: Implementing Continuous Testing Effectively
47mHow Testing is Evolving in DevOps