It's not your test framework, it's you
summary
Claim: brittle suites come from misuse not Cucumber or RSpec. Demonstrated with a Twitter example that repeatedly embeds UI steps like click button tweet and login Bob, causing duplicated assumptions and slow builds (examples: 18 minutes 3 hours and a horror story of 33 hours). Remedies shown include extracting a domain DSL, stubbing authentication, quarantining flaky tests, removing sleeps, classifying tests into journey functional integration and unit and deleting low-value specs so acceptance tests become readable, fast, and actionable.
AI-written summary · about
chapters (19)
- 0:00Sustainable BDD practices
- 1:27BDD origins and misunderstandings
- 3:34Collaborating with product owners
- 7:46BDD tools and Gherkin
- 9:54Gherkin for application state
- 11:59Avoiding brittle BDD tests
- 14:25Pitfalls of UI automation
- 17:11Domain-specific test languages
- 19:17Why PO collaboration matters
- 20:40Living executable documentation
- 22:25Slow test suites impact
- 24:11Flaky tests and sleeps
- 27:03Quarantining flaky tests
- 28:27Deleting outdated tests
- 29:29Reducing redundant tests
- 31:15Over-testing balance
- 34:01Optimizing test suites
- 34:43Test code as first-class
- 35:03Embracing BDD fully
