How Are We Supposed to Know what We Should Create?
summary
Claims a three-step procedure for Behavior-Driven development that actually yields the right software: discover with example mapping on paper (timebox ~25 minutes), formalize examples in gherkin stored in version control, then implement with TDD and automated acceptance tests (Cucumber, Java/Maven). Demo wires executable specs to code using a vending‑machine coffee example, runs one scenario with four steps (later two scenarios eight steps), and treats the acceptance tests as the safety net that proves the behaviour works.
AI-written summary · about
chapters (8)
- 0:00Start
- 6:27The Three Amigos
- 7:40Example Mapping
- 13:33Gherkin
- 19:36Demo
- 29:41End Goal
- 31:13Behavior Driven Development
- 33:36What Is the Difference between Tdd and Bdd
related talks
45mBehaviour Driven Development: Embrace Uncertainty
45mLet's talk about software behaviour (BDD)
17mUnlocking Collaboration in Code: A Journey through BDD
41mBehavior-Driven Development: Feature this!
01h 04mDriving Design through Examples
45mBehaviour Driven Development and Behat: Telling Stories Through Code
50mAn introduction to Behaviour Driven Development (BDD) for embedded systems
53mBehaviour Driven Development, BDD, with Cucumber for Java