Isn’t Test Automation a Silver Bullet?
summary
Automation cuts manual runs but still demands continuous upkeep because agile changes break tests and missing updates cause coverage gaps. UI tests become brittle unless devs add data-test-id hooks; pipelines slow unless tests run on parallel VMs and slow tests are trimmed after timing analysis. Hardware and AI features often need simulation or probe interfaces since sensors and models resist full automation. Frequent false positives require static code analysis and peer review plus collected execution evidence and root-cause fixes.
AI-written summary · about
chapters (8)
- 0:00Start
- 1:51Frequent Updates/Changes
- 4:19Unstable Behaviors
- 5:34Testability
- 6:33Hardware
- 8:50Perception handling
- 9:44Not always easy to build / set up
- 10:46Not always easy to figure out
related talks
46mWhy Is Test Automation Still Manual and How Can We Make It Really Automated?
13mBeyond the hype: What test automation really costs
01h 08mTest Automation Monsters
38mDo We Really Need A Test Automation Engineer?
24mWHY ARE WE FAILING WITH TEST AUTOMATION?
51mRedefining test automation
21mThe Essential Pillars of Automation Testing for Success
47mPanel Discussion: Future of Test Automation