"Effective ways of using BDD concept for Testing"
summary
Argues that BDD is not just plain-language test scripts but a collaborative workflow where three amigos produce acceptance criteria in Gherkin, testers convert those criteria into automated acceptance tests using Cucumber features, and teams integrate the resulting suites into an Azure Release pipeline so failures are triaged with developers. Shows tester responsibilities: join specification sessions, automate acceptance tests, collaborate on failures, and build and maintain the automation framework to reduce miscommunication and speed delivery.
AI-written summary · about
chapters (6)
- 0:00Intro
- 1:50BDD - A Catalyst For Agile
- 3:29Traditional Workflow
- 5:30BDD Workflow
- 6:19Gherkins
- 6:55Tester's Role
related talks
48mBDD - It’s More Than Acceptance Tests
34mDaniel Horn: BDD is Not a Testing Approach - How to Overuse BDD to Slow Down Your Delivery
45mLet's talk about software behaviour (BDD)
41mBDD Crash Course for Testers
36mBDD With Cucumber
51mDoes BDD Adds Additional Architectural Limitations on Solutions for Testing?
48mMake Your Life Simple and Carefree with BDD
01h 05mContrasting Test Automation and BDD: An "Interactions Over Tools" Perspective