Why your next QA job might be in Ops
summary
Argument: traditional manual QA roles are disappearing as delivery pipelines and infrastructure become code and automation eats rote checks. The talk claims CI/CD and IaC need explicit testing, even of the pipeline itself — examples include using terraform plans and validating deployments — and asserts the pipeline should be more resilient than the product. Expect recommendations to shift into performance, security, compliance and production experiments, with emphasis on test infrastructure-as-code and chaos engineering and on ML replacing brittle Selenium scripts.
AI-written summary · about
chapters (32)
- 0:00Intro
- 0:57Who am I
- 1:48Preface
- 2:01Continuous Quality
- 3:20Who like testers
- 3:49Who like to break things
- 5:33What is QAx job
- 6:14What does QA do
- 7:20QA and Ops
- 8:30Traditional QA
- 9:33Cost of failure
- 9:54Agile
- 10:54Operations
- 11:39MVPs
- 12:12Remediation
- 12:22Troubleshooting
- 12:38Automation
- 13:16Cloud
- 13:32Deployment Automation
- 13:43Automation Apocalypse
- 14:43Your golden time
- 15:46Business starving for information
- 16:10Experimental mindset
- 17:06Resilience
- 17:37Profiling
- 18:44Compliance
- 19:23User Monitoring
- 20:06Chaos Engineering
- 20:18Netflix
- 21:39Hardware
- 22:09Conclusion
- 22:39QA vs Ops
related talks
06mDoes QA have a place in DevOps? Heck yeah!
47mHow Testing is Evolving in DevOps
20mEnsuring Quality in DevOps Culture
44mQA in a Pipeline Based Organization
35mTestOps? well, Never mind
27mExploring a DevOps Transformation Like a Tester
41mQuality Transformation
52mCreating a QA/DEV Collaborative Testing Strategy