What Successful Test Automation is... and Why it's NOT Testing!
summary
Argues that test automation is a means, not testing itself, and that teams must measure actual value not vanity counts: only 26% value in top three. Cites a Pfizer stat that a passing test has less than 3% chance to find future bugs. Recommends shifting from brittle UI‑only suites toward dynamic dedicated fresh environments (infra as code, isolated data), using the FITR: focused informative trustworthy repeatable criteria and a test‑suite canvas to pick and maintain only high‑value automations.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 5:53Effective software testing
- 9:03Test automation state
- 11:14Test automation myths
- 15:47Missing automation objectives
- 20:03Effective automation traits
- 23:17FITR criteria for test value
- 25:46Stable test environments
- 29:15Test Suite Canvas
- 31:23Broader automation definition
- 33:53Impact on testing craft
- 35:59Key takeaways
- 38:07Q&A: Starting automation
- 41:35Q&A: Evaluating tests
- 44:03Q&A: Certification expectations
related talks
13mBeyond the hype: What test automation really costs
51mRedefining test automation
38mDo We Really Need A Test Automation Engineer?
40mThe Test Automation Firehose
42mOpening Keynote: Blunders in Test Automation
44mThe Test Automation Pyramid and How It Ruins Your Life
21mThe Essential Pillars of Automation Testing for Success
01h 08mTest Automation != Less Testers || Faster Testing || More Time For ET