Behaviour Driven Development: Embrace Uncertainty
summary
Argues BDD is about conversations using concrete examples, not tools, citing JBehave and Cucumber as historical tools but stressing examples like refunding a £100 microwave to reveal contexts (damaged, no receipt, discount) and outcomes (stock increment, debit account). Shows a pattern: give me an example to elicit scenarios, use the three amigos (product expert, developer, tester), probe risky, novel capabilities first, spike prototypes for complex uncertainty, and treat automation as a later side effect of clarified behavior.
AI-written summary · about
chapters (13)
- 0:00Start
- 10:16The Only Outcome That Matters
- 15:48Acceptance Criteria versus Scenarios
- 17:57Why this Is Important
- 19:47Three Amigos
- 20:11Critical Thinking Testers
- 21:30Who Should Write the Scenarios Down
- 23:43First Mobile Phone
- 27:05The Leaders Framework for Decision-Making
- 27:19Obvious Domain
- 36:37Boundary of Influence
- 38:25The Agile Manifesto
- 39:56Exploring by Example
related talks
41mBehavior-Driven Development: Feature this!
17mUnlocking Collaboration in Code: A Journey through BDD
48mMake Your Life Simple and Carefree with BDD
48mBDD - It’s More Than Acceptance Tests
31mBDD: Behaviour Driven Development
50mAn introduction to Behaviour Driven Development (BDD) for embedded systems
45mBehaviour Driven Development and Behat: Telling Stories Through Code
48mMake Your Life Simple and Carefree with BDD