WHY ARE WE FAILING WITH TEST AUTOMATION?
summary
Company QA reports that automation stalls because specifics are missing: built a custom framework and function libraries but tests target generic “smart” flows instead of specific, high‑value checks; tooling choices matter — used Selenium driving Firefox that broke after auto updates and required dedicated hardware and environments; process failures include no documentation, no schedule alignment with agile teams, and missing metrics — measured ROI and run‑counts rarely tracked so maintenance cost and real value stay unknown.
AI-written summary · about
chapters (4)
- 0:00Start
- 10:06#1- Changing Environment Changing Business What can be the consequences?
- 14:19#2 - I will do your work What are the risks?
- 17:35NO NEED FOR AUTOMATION 38
related talks
16mIsn’t Test Automation a Silver Bullet?
38mDo We Really Need A Test Automation Engineer?
50mAsaf Shochet Avida, Eitan Noy: Why My Amazing Test Automation Project Crumbled
21mThe Essential Pillars of Automation Testing for Success
46mWhy Is Test Automation Still Manual and How Can We Make It Really Automated?
01h 08mTest Automation Monsters
40mRules of Engagement QUESTIONS TO ASK BEFORE YOU START AUTOMATING
47mWhat Successful Test Automation is... and Why it's NOT Testing!