Living on crotches or UI Automation antipatterns
summary
Covers concrete UI automation anti‑patterns and fixes: the ice-cream cone and cupcake testing pyramids that leave too few unit tests and too many brittle UI tests; misused Rube Goldberg machine architectures that bloat setup and block junior entry; mistaken BDD use with tools like Cucumber SpecFlow JBehave that add glue code without stakeholder buy‑in; specific fixes—plan with devs and testers, split conditional tests, prepare preconditions, externalize configs, prefer simple design, and use Hamcrest matcher‑style assertions so failures say exactly what broke.
AI-written summary · about
chapters (17)
- 0:00Intro
- 1:25Why crutches?
- 2:08What is an antipattern
- 2:39Crutches in real life vs coding
- 5:00Levels
- 6:53The Nr 1 Antipattern
- 7:45Testing pyramid antipatterns
- 8:33Ice-cream cone
- 9:22Where does it come from?
- 10:31Cupcake
- 12:31Fast and Furious!
- 16:21Stay positive, bro!
- 18:20Breaknig B.DDI
- 22:36Rube Goldberg Machine
- 27:08What if
- 30:27Only hardcode!
- 34:13Something's broken!
related talks
32mLiving on Crotches or UI Automation Antipatterns
57mAdvanced Testing Techniques: Tips from the trenches
33mMore Than Automation: How Good Acceptance Test Can Make Your Team Happier
36mIt's not your test framework, it's you
48mDesign patterns to boost your test automation
36mIt's not your test framework, it's you
58mTesting Strategy - New Model, Better Outcomes
47mThe secret unit testing tools no one ever told you about