Eschew Obfuscation and Omit Needless Words: Writing Clear Acceptance Tests

on YouTube ↗31m

" summary

The claim is concrete: edit verbose Cucumber scenarios into intention‑revealing tests that state the actual assertion and hide incidental UI steps. Concrete moves include collapse field fills into "make an offer", hide setup in Background or helper steps, use tables and scenario outlines to express complex bid/offer matrices, and allow flexible phrasing with regex so business language maps to test steps. Also separate UI‑specific checks into dedicated UI scenarios and keep acceptance tests focused on domain intent.

AI-written summary · about

" chapters (8)

1. 0:00Intro
2. 3:10Being Nice
3. 4:50Example
4. 6:55Rule 13 Words Details
5. 8:40Rule 14 Words Details
6. 12:05Regular Expressions
7. 18:40Conclusion
8. 22:35George Orwell

" related talks

• 01h 00mAcceptance Testing Sounds Easy, But Is Hard to Get RightPeter Gfader · TestCon Europe 2021
• 34mWriting end to end tests with a smileEkaterina Budnikov, Kim Hogeling · GDG DevFest Hamburg 2017
• 33mMore Than Automation: How Good Acceptance Test Can Make Your Team HappierMatt Wynne · SeleniumConf 2012 London
• 36mLiving on crotches or UI Automation antipatternsVadzim Zubovich · TestCon Vilnius 2017
• 40mHow Cucumber Can Improve Your TestingTitus Fortner · Selenium Conference 2013
• 35mCucumber: Automating the Requirements Language You Already SpeakBen Mabey · Agile Roots 2010
• 36mIt's not your test framework, it's youRobbie Clutton, Matt Parker · LA RubyConf 2013
• 25mWriting end to end tests with a smileEkaterina Budnikov · HUSTEF 2018