"TestOps: Chasing the White Whale"
summary
Describes practical TestOps work: choosing AWS instance families (M1/C1/C3/C4), staging a clone, and using production monitoring as the oracle to validate migrations; a database table shows a 10x slowdown discovered by monitoring, fixed before user impact; a DNS cutover is later turned into an automated DNS flip after a failed rehearsal; reproducing a denial‑of‑service attack shows scaling only bought five minutes, proving the need for code/database fixes rather than bigger instances.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:03Why TestOps matters
- 4:33Testers and operations
- 9:09Moving to the cloud
- 14:08What is an oracle
- 16:34The Great environment migration
- 22:28Can't scale horizontally
- 26:26What's next for TestOps
- 33:53Building TestOps teams
- 37:04Q&A
related talks
43mBest practices for continuous testing and observability
15mDevOps at scale
15mTransforming Testing: The Power of TestOps
01h 08mPerformance testing in the cloud
46mA Practical Guide to Testing in DevOps
28mHow Not-To Test in Production: Learnings from DoorDash
55mDevOps @Scale (Greek Tragedy in 3 Acts)
31mTesting in Production