Chaos Survival Guide: How to Start Testing if There is Nothing to Help You
summary
Practical checklist for getting testing started on a project with nothing: gather information about goals users integrations and timelines then iterate those goals as new facts appear; pick essentials not everything; introduce one or two metrics first and validate them; decide concrete automation scope (API vs UI) and consider BDD practices if requirements are in natural language; use the Deming cycle to plan do check act; example shows a live mobile game where automation and user feedback channels reduce regression risk.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 1:31Chaos in testing projects
- 2:35Gathering info and goals
- 5:23Project landscape mapping
- 6:27Info gathering strategies
- 9:18Structured questioning
- 10:43Testing scope and objectives
- 11:50Testing approaches and techniques
- 13:16Resources and tools needed
- 13:56Refining goals
- 15:45Deming cycle changes
- 17:58Case study: chaos survival guide
- 21:38Conclusion
- 22:40Q&A
related talks
23mChaos Survival Guide: Start testing in any conditions
40mRules of Engagement QUESTIONS TO ASK BEFORE YOU START AUTOMATING
43mCan you Test it
45mBuilding Tools to Free up Exploratory Testers
46mThe Practical Automation Playbook
49mWhat if your survival depended on…
24mExploratory: Testing Humanely, Checking Robotically
53mEarly Performance Testing: Finding News You Can Use