The Automation Firehose Be Strategic and Tactical
summary
Argues that teams must stop the "automation firehose" and prioritize tests by value using an automation scorecard that ranks frequency, business impact, setup complexity and reuse. Shows a real Gherkin Azure DevOps UI test built with Selenium over Ruby+Cucumber, warns against 300‑step flaky scripts, and recommends unit→service→UI→E2E ordering, single‑assertion tests, treating tests as code with refactoring and CI gating so automation runs concurrently and actually reduces risk.
AI-written summary · about
chapters (8)
- 0:00Introduction and speaker background
- 1:46Strategy vs tactics in automation
- 3:08Deciding what to automate
- 5:54Automation scorecard and prioritization
- 7:19Choosing automation tools and frameworks
- 9:06Common automation challenges
- 11:36Automation and development workflow
- 11:57Key takeaways and conclusion
related talks
40mThe Test Automation Firehose
51mRedefining test automation
09m“Guide to creating your test automation strategy”
21mThe Essential Pillars of Automation Testing for Success
13mBeyond the hype: What test automation really costs
08mReviewing your test automation strategy"
38mDo We Really Need A Test Automation Engineer?
52mHow to win with automation and influence people