Chaos - Does It Need to Be Included in Test Strategy?
summary
Chaos engineering is experimental production testing that deliberately induces failures to prove resilience, born from Netflix’s 2012 outage; it follows four steps — hypothesis, testing, blast radius, insights — runs on planned game day (2–4 hours), and requires objectives, KPIs, selected targets, metrics and team readiness. Tools mentioned include Chaos Monkey, Gremlin, Chaos Toolkit; start with small blast radii and increase until failure, and treat findings as action items. Include it in strategy when systems handle billions of transactions.
AI-written summary · about
chapters (7)
- 0:00Start
- 2:36Introduction to Chaos Engineering
- 3:19History
- 5:31Prerequisites
- 6:21Game Day
- 7:37How does it work?
- 10:14Available Chaos Tools
related talks
18mChaos Engineering: Break It On Purpose
37mUse Chaos Testing to Build Resilience in the Software
46mDesigning a System for Chaos
36mChaos Engineering
52mChaos engineering: Breaking things on purpose in production
48mChaos Engineering: The Path to Reliability
23mHow to tame chaos effectively?
38mChaos Engineering