TestOps? well, Never mind
summary
Argues that “TestOps/QA Ops” is not a new silo but testing must be integrated into DevOps to fix three concrete failures: layers of test environments that duplicate work, more than 50% unreproducible bugs caused by config and test data mismatches, and fragile external integrations that account for over 70% of failures in some setups (23% for payments in retail). Describes attempts to add a test management tool that fails behind VPN/IP and CI/CD gaps, and calls for ops to provide reproducible infra, sane environment gating, and tool choices that actually plug into CI pipelines.
AI-written summary · about
chapters (9)
- 0:00Introduction and context
- 2:31What is TestOps
- 7:06DevOps and testing synergy
- 13:06Shift left in testing
- 14:52Key challenges in testing
- 26:04Collaboration and efficiency
- 28:35Q&A: Segregation of roles
- 30:21Q&A: Cost and innovation in testing
- 34:17Closing remarks
related talks
15mTransforming Testing: The Power of TestOps
06mDoes QA have a place in DevOps? Heck yeah!
29mWhy your next QA job might be in Ops
47mHow Testing is Evolving in DevOps
41mDevOps! Let's Change QA!
20mEnsuring Quality in DevOps Culture
25mDevOps Bringing a New Concept to Software Quality
32mWhy Testing is fundamentally different in DevOps than Classic Projects
