"BDD: NOT The Given-When-Then Thing"
summary
Claims that BDD equals Cucumber or Given-When-Then misuse are false and costly: structured collaboration is the point. Teams that adopt example mapping and feature mapping and keep conversations, examples and rules as executable specifications see defects drop as much as 80–90% after 6–9 months. Adding Gherkin only for UI automation without those conversations yields brittle, hard-to-maintain tests; when done right BDD produces clear business-readable rules, faster feedback and maintainable automated regression.
AI-written summary · about
chapters (4)
related talks
34mDaniel Horn: BDD is Not a Testing Approach - How to Overuse BDD to Slow Down Your Delivery
52mBDD: Truly Collaborating with the Business
49mBDD Is Not Test Automation
48mBDD - It’s More Than Acceptance Tests
40mMaking BDD Work for you
16mBDD with cucumber.js
17mUnlocking Collaboration in Code: A Journey through BDD
01h 05mContrasting Test Automation and BDD: An "Interactions Over Tools" Perspective