Chaos Survival Guide: Start testing in any conditions
summary
Chaos survival here means a concrete workflow not pep talk: use the PDCA cycle to make incremental changes, deploy only what you can measure, and roll back if metrics don’t improve; gather facts with structured interviews and telemetry, not vague assumptions; use the mind map (QR code) to ask exactly which features, integrations and data are in scope; run a focused investigation like the mobile game case: bug hypothesis vs UX that tests whether low users map to crashes or to experience, then prioritize fixes.
AI-written summary · about
chapters (10)
- 0:00Surviving chaos in testing
- 1:13Chaos reaction and challenges
- 3:02Goals and project landscape
- 5:52Stakeholder information gathering
- 7:44Testing scope and approach
- 10:54Prioritizing tasks
- 13:06PDCA cycle implementation
- 14:33Testing strategy example
- 16:19Key takeaways
- 17:26Q&A
related talks
23mChaos Survival Guide: How to Start Testing if There is Nothing to Help You
15mChaos - Does It Need to Be Included in Test Strategy?
49mWhat if your survival depended on…
37mUse Chaos Testing to Build Resilience in the Software
18mThe Good, the Bad and the Ugly: The 3 Learnings of an SRE
01h 34mShift left in testing: Find bugs before they’re implemented
41mSheekha Singh: You cannot TEST everything
06m"Outperforming in the Chaotic World!"