Tree in the forest: managing details in BDD scenarios
summary
Scenarios often explode with execution-only details, and the concrete claim is that applying the essential principle — keep only details that change the outcome — makes scenarios readable and spec-like. Tools named are Cucumber and SpecFlow and automation must push down to automation where defaults create required entities and random or code-generated data. Teams log generated values for visibility via logs, agree defaults, and reuse code so specs stay stable while tests still run.
AI-written summary · about
chapters (14)
- 0:00BDD introduction
- 1:11Why details matter
- 4:22Scenarios as tests
- 6:30Details in BDD scenarios
- 8:38Details in scenarios vs code
- 12:55Scenarios as specs
- 17:06Essential vs incidental details
- 17:27Details to push down
- 20:54Managing BDD details
- 21:38Q&A: Replace requirements?
- 21:58Q&A: BDD with TDD/ATDD
- 23:01Q&A: Acceptance criteria
- 23:44Q&A: End user involvement
- 24:46Q&A: Scenarios and abstraction
related talks
24mFighting against technical debt with BDD, DevOps and Sustainability
40mMaking BDD Work for you
16mBDD with cucumber.js
36mBDD With Cucumber
48mMake Your Life Simple and Carefree with BDD
08m"BDD: NOT The Given-When-Then Thing"
57mSetting a Good Example - How to improve your SbE, BDD & ATDD Artefacts
41mWriting better BDD scenarios