It's not your test framework, it's you
summary
Claim: brittle slow suites come from misuse not from Cucumber or Capybara. Root causes are cargo‑culted BDD, scattered UI details, sleeps and duplicated login flows. Concrete fixes: groom features into journey functional integration and unit tests, extract a domain DSL and shared web helpers, replace sleeps with Capybara polling, quarantine flaky tests and delete tests that add no value. Measured horrors include builds of 18 minutes or even 33 hours — trim authentication calls and tag authenticated tests to get under a minute.
AI-written summary · about
chapters (16)
- 0:00Sustainable BDD practices
- 1:10BDD hype and pain points
- 2:55Cargo cult and Dan North
- 3:59Collaborating on criteria
- 12:05Brittle tests fail intent
- 14:34Big pets and UI testing
- 17:22Domain-specific test language
- 19:28Product owners avoid BDD
- 20:51Executable documentation challenges
- 22:33Slow and flaky suites
- 24:19Prayer-driven development
- 26:28Quarantine flickering tests
- 28:13When to delete tests
- 29:17Over-testing strategies
- 31:23Confidence versus speed
- 34:11Key takeaways
related talks
34mEliminating Inconsistent Test Failures
26mNot your unit test
32mLiving on Crotches or UI Automation Antipatterns
36mLiving on crotches or UI Automation antipatterns
34mWriting end to end tests with a smile
29mCommon Mistakes that make test cases flaky and how to avoid them
28mTDD: When the thrill has gone
48mTesting Should Be Fun