The Test Automation Firehose
summary
Argues for targeted automation: prioritize unit tests, then service, then UI, score candidates with an automation score (0–100) and use a checklist for feasibility; warns that automation is another codebase with maintenance cost and technical debt. Recommends aligning tools with the stack — e.g. Ruby Cucumber or Selenium for web — keep short single‑purpose functional tests, control data/environments, run regression reviews and code reviews, and notes a team of eight supporting 73 apps (407 web) as a cautionary scale.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 2:36Background
- 7:59Approach
- 13:50Tools
- 18:21Challenges
- 23:32Example Mapping
- 26:35Standards
- 28:05Code reviews refactoring
- 30:18Summary
- 31:30QA Question
related talks
13mThe Automation Firehose Be Strategic and Tactical
51mRedefining test automation
13mBeyond the hype: What test automation really costs
38mDo We Really Need A Test Automation Engineer?
09m“Guide to creating your test automation strategy”
08mReviewing your test automation strategy"
55mShifting the Testing Role Pendulum
47mWhat Successful Test Automation is... and Why it's NOT Testing!