Better Bullshit-Driven Development
summary
Argues that BDD often becomes “Bullshit Driven Development” when teams write Gherkin and boilerplate steps just for readability. Proposes using Selenium/Selenide, Allure, fluent page objects and a single application-manager entry point to keep tests as idiomatic xUnit while adding readable context: implement no-op annotated “pseudo-steps” for Allure and reusable page-returning methods. Reports show clearer Allure output, less duplication, easier onboarding, and practical effectiveness (not a silver bullet).
AI-written summary · about
chapters (10)
- 0:00Introduction
- 4:38xUnit examples
- 8:57Acceptance Test Driven Development
- 14:45BDD client problems
- 15:07Allure Reports
- 20:59Single Page Object
- 25:33Pseudo-steps in Allure
- 29:55Improving ATDD
- 33:14When to use BDD
- 35:03Q&A
related talks
34mDaniel Horn: BDD is Not a Testing Approach - How to Overuse BDD to Slow Down Your Delivery
48mBDD - It’s More Than Acceptance Tests
09m"Effective ways of using BDD concept for Testing"
23mBDD To The Bone: Acceptance Testing with Behave and Selenium
34mWriting end to end tests with a smile
40mMaking BDD Work for you
45mBehaviour Driven Development and Behat: Telling Stories Through Code
51mDoes BDD Adds Additional Architectural Limitations on Solutions for Testing?