What is Context-Driven Testing?
summary
Asserts testing decisions hinge on specifics not slogans: the seven principles state practices depend on context and there are no universal best practices; exploratory work finds surprises (two demo cubes turn out to be magnesium and tungsten with a factor of almost eleven in density). Warns automation isn’t a substitute for human sense-making, calls test cases artifacts not the activity, cites HP Quality Center as costly sunk‑cost example, notes a lively community (~3000 people in Slack and Ministry of Testing).
AI-written summary · about
chapters (9)
- 0:00Intro
- 2:44Observations
- 3:28What is a tester
- 10:59Testing
- 16:18ContextDriven Testing
- 21:51Community
- 27:04Checking and experimentation
- 31:10Automation
- 39:36Jesse Alfred Story
related talks
49mESSENTIALS - Canon Test-Driven Development
26mCynefin & Test Planning - an Option for Choosing the Right Testing Approach
01h 15mFrom Test Cases to Context-Driven: A Startup Story
53mTesting without dogma
45mBehaviour Driven Development: Embrace Uncertainty
42mDesign Driven Concepts for Automated Testing
37mClean Test Code
05mContext-Driven Practices