Contrasting Test Automation and BDD: An "Interactions Over Tools" Perspective
summary
Argues that BDD and test automation solve different problems: BDD is a three-practice loop—discovery, formulation, automation—producing business-readable specs and earlier learning, while test automation is a broader technical effort often delivered later and siloed. Calls out Cucumber (and Gherkin given/when/then) as a tool that got conflated with BDD, notes immature tooling (Cucumber Studio, Behave Pro attempts), and gives concrete failures: banks needing to boot separate hardware and set the system clock, brittle Selenium record‑and‑playback suites, teams spending mornings fixing broken tests.
AI-written summary · about
chapters (18)
- 0:00Intro
- 1:28Agenda
- 3:40Polls
- 7:42Agile
- 9:28Cucumber
- 10:37Test Automation
- 11:10Test Automation Definition
- 12:09Benefits of Test Automation
- 18:02Challenges of Test Automation
- 19:56Testability
- 22:48Late Feedback
- 24:56Kellys Heroes
- 27:07Interactions
- 29:35BDD
- 36:41Challenges
- 42:41Discovery
- 47:56Integration
- 54:26Comparison
related talks
09m"Effective ways of using BDD concept for Testing"
49mBDD Is Not Test Automation
08m"BDD: NOT The Given-When-Then Thing"
48mBDD - It’s More Than Acceptance Tests
34mDaniel Horn: BDD is Not a Testing Approach - How to Overuse BDD to Slow Down Your Delivery
51mDoes BDD Adds Additional Architectural Limitations on Solutions for Testing?
45mBehaviour Driven Development: Embrace Uncertainty
36mBDD With Cucumber