Confused Tester in Chaotic World
summary
Case study of a contact‑center platform that serves 40K+ agents shows chaos testing using VMware APIs to cut inter‑node communication, PowerShell to kill processes, latency injection and load spikes up to 200 calls/sec; hypothesis: no active calls drop and standby site takes over automatically; focus shifts from MTTF to mean time to recover (MTTR) and tests measure failover time (established calls recover in fractions of milliseconds) and reduce outage impact.
AI-written summary · about
chapters (7)
- 0:00Start
- 2:59The Confused Tester in Chaotic World
- 12:45Expected State
- 13:51Chaos Experiment
- 17:36Challenges
- 18:00Define a Hypothesis
- 18:47Chaos Monkey
related talks
46mChaos Experiments - Datacenter Stress Testing
37mUse Chaos Testing to Build Resilience in the Software
06m"Outperforming in the Chaotic World!"
44mChaos Engineering for SQL Server
19mLearnings from Chaos experiments
33mTesting at the Speed of Agents: Salesforce's Evolving Approach to Agentic Testing
48mTesting The Cloud
15mChaos - Does It Need to Be Included in Test Strategy?
