Seven Proven Ways to Ruin Your Test Automation
summary
This talk lists seven concrete failure modes that destroy test automation: hoarding knowledge in a single ‘knowledge champion’, vendor tool lock-in, brittle capture‑replay scripts, automating fragile/manual workflows and interdependent tests, pretending management support, setting impossible targets, and developers constantly changing UI objects. For each problem it points to explicit test automation patterns and modular design practices (documented on a patterns wiki) as the countermeasures.
AI-written summary · about
chapters (6)
- 0:00Introduction
- 3:51Ignoring docs
- 7:54Unrealistic expectations
- 12:12Overcomplicating scripts
- 16:20Lack of maintenance
- 20:33Management's role
related talks
55mTop 5 Pain Points of Test Automation
54mTest Automation Transformation Avoiding the 7 Common Pitfalls
42mOpening Keynote: Blunders in Test Automation
40m10 Automation Principles I Will Not Betray
44mThe Test Automation Pyramid and How It Ruins Your Life
38mDo We Really Need A Test Automation Engineer?
50mWhy Everything Is Spoiled
47mAnti-patterns and smells in test automation
