BDD Is Not Test Automation
summary
Explains what Behaviour-Driven Development (BDD) should and should not be used for: recommends using BDD techniques to share business understanding among teams, and advises against writing Gherkin-style scenarios for UI test cases. Mentions practical guidance drawn from software quality and testing practice in agile contexts.
AI-written summary · about
chapters (6)
- 0:00BDD controversy
- 10:09What BDD really is
- 27:36Understanding requirements
- 36:16Correct BDD process
- 40:52Unit-level automation
- 48:59Q&A
related talks
31mBDD: Behaviour Driven Development
34mDaniel Horn: BDD is Not a Testing Approach - How to Overuse BDD to Slow Down Your Delivery
41mBDD Crash Course for Testers
48mMake Your Life Simple and Carefree with BDD
52mBDD: Truly Collaborating with the Business
48mBDD - It’s More Than Acceptance Tests
08m"BDD: NOT The Given-When-Then Thing"
48mMake Your Life Simple and Carefree with BDD