Does BDD Adds Additional Architectural Limitations on Solutions for Testing?
summary
Claims that BDD acts primarily as a risk‑management tool for shaping stable requirements, shows concrete mappings from Gherkin to generated tests and reports, and catalogs tools: Selenium, Cucumber/SpecFlow, Serenity, Spring, RestAssured, Apache HttpClient, Postman and standard HTTP + JSON/XML parsers. Demonstrates code and architecture diagrams, argues BDD itself doesn’t force architectural constraints though Serenity enforces an opinionated architecture, cites 99% of cases where alleged BDD limits are misunderstandings and notes Scrum can be ~15% costlier, while backend BDD uses plain HTTP clients and unit test frameworks with successful examples.
AI-written summary · about
chapters (5)
- 0:00Start
- 2:20What's Bdd Is Behavior Driven Development
- 22:53Business Actions
- 23:26What Does Bdd Do
- 26:45The Benefits
related talks
48mBDD - It’s More Than Acceptance Tests
09m"Effective ways of using BDD concept for Testing"
34mDaniel Horn: BDD is Not a Testing Approach - How to Overuse BDD to Slow Down Your Delivery
24mFighting against technical debt with BDD, DevOps and Sustainability
08m"BDD: NOT The Given-When-Then Thing"
49mBDD Is Not Test Automation
16mBDD with cucumber.js
41mBDD Crash Course for Testers