More Than Automation: How Good Acceptance Test Can Make Your Team Happier
summary
Claims that browser automation written as clicks and form fiddling becomes brittle and hides domain meaning and shows concrete refactorings that cause this: conflate scenarios and stuffing in incidental detail that anchors tests to copy and CSS. Recommends writing features at a higher declarative style level, using Cucumber as living documentation, collaborating with domain experts, and keeping step definitions well factored. Shows a working tool called Relish that publishes feature files (read‑only beta, CLI for private projects, later paid).
AI-written summary · about
chapters (10)
- 0:00The philosophy of MDD
- 3:28Cucumber as a perceived threat
- 5:37Refactoring for unmaintainability
- 9:56Reviewing the MDD impact
- 11:42Bridging the gap with Cucumber
- 17:27Documentation vs testing
- 20:24Declarative vs imperative
- 23:44Getting feedback and tooling
- 25:49Concluding best practices
- 28:22Q&A and closing
related talks
42mThe automated acceptance testing paradox
51mRedefining test automation
34mWriting end to end tests with a smile
36mLiving on crotches or UI Automation antipatterns
21mThe Essential Pillars of Automation Testing for Success
09m"Effective ways of using BDD concept for Testing"
40mThe Test Automation Firehose
32mLiving on Crotches or UI Automation Antipatterns