Are companies chasing a quality mirage in the era of cloud, devops, SaaS & others
summary
Companies claim their testing will catch 1000 critical bugs and reduce testing time by 1000x while migrating monoliths to microservices, but they actually keep old test models, ignore integration and end-to-end responsibility, and run 100% automation dashboards that mean little. CI/CD pipelines, container and Kubernetes behavior, test data from golden images, and performance tests with wrong concurrency or volumes remain untested, so systems fail in production despite green dashboards and optimistic SLAs.
AI-written summary · about
chapters (12)
- 0:00Introduction to quality mirage
- 1:05The desert explorer analogy
- 2:54Why quality becomes a mirage
- 3:57Testing challenges in microservices
- 6:30Cloud and microservices complexity
- 7:53Agile testing pitfalls
- 9:17Collaboration gaps in quality
- 10:42CI/CD pipeline testing gaps
- 12:37Performance testing neglect
- 13:40Automation misconceptions
- 15:06The illusion of 100% testing
- 15:49Conclusion and credits
related talks
01h 08mTest Automation Monsters
27mYour Roadmap to Continuous Delivery and Continuous Testing
32mTales from the DevOps Transformation Trenches
16mChallenges of Testing at Scale | Experiments and Experiences
20mEnsuring Quality in DevOps Culture
49mPanel Discussion: Mission-Critical Priorities in Quality Engineering: The Leader's Playbook
26mThe Impact of Testing on a DevOps Pipeline
06mLightning Talk: Automated Testing Done Right