Learning to speak a common language with BDD and pickled cucumbers
summary
Team adopts behave and Gherkin/Cucumber to write executable Given When Then scenarios, spends about two to four months in a BDD-first phase using domain-driven design, then delays heavy tech like databases until feature files clarify data shape. Implementation builds an adherence feature that detects on-time or late bus arrivals and finally shows buses on a map. Automated tests break after refactors but feature files remain accurate and valuable for interactive verification, prompting a renewed commitment to BDD.
AI-written summary · about
chapters (28)
- 0:00Intro
- 1:40GoMetro
- 3:27What is BDD
- 3:57BDD library
- 6:31Three Amigos
- 7:45Showdown Tile
- 8:15Demo
- 8:39Feature File
- 10:45Context
- 11:22Adherence
- 13:36Coding
- 20:41Back to slides
- 21:04Real world example
- 23:23Review sessions
- 25:22Broken tests
- 26:09useless tests
- 27:30wrapping things up
- 28:39afrolabs
- 30:12Jade
- 30:40Benjamin
- 31:39Project time
- 33:03More questions
- 33:44Using BDD with other tools
- 34:51Is BDD dependent on exact phrasing
- 36:13When is a good time to use BDD
- 36:51Use cases
- 37:26Data science
- 38:16BDD vs endtoend testing
related talks
16mBDD with cucumber.js
36mBDD With Cucumber
08m"BDD: NOT The Given-When-Then Thing"
45mLet's talk about software behaviour (BDD)
50mAn introduction to Behaviour Driven Development (BDD) for embedded systems
09m"Effective ways of using BDD concept for Testing"
26mNot your unit test
34mDaniel Horn: BDD is Not a Testing Approach - How to Overuse BDD to Slow Down Your Delivery