Asaf Shochet Avida, Eitan Noy: Why My Amazing Test Automation Project Crumbled
summary
A three‑person team builds an ambitious test automation suite over ten months that sits unused in Git after 18 months; they automate an internal QA form with Selenium/Cypress/Playwright and discover internal‑tool hops create hidden dependencies, repeated UI logins become a single point of failure so they recommend bypassing login via API or a dedicated login suite, flakiness kills trust so they advise to kill flaky tests (example: 3 flaky out of 1,000) and to run new tests 25 times before merging and store failed run videos in S3.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 1:08Automation project origin
- 6:12Mimicking manual tests
- 11:30Login flow duplication risks
- 16:03Fixing test flakiness
- 21:22Hybrid tester myth
- 25:23Prioritizing test coverage
- 29:16Automation customers
- 33:56Test timing and CI/CD
- 37:28System awareness in automation
- 40:59Key takeaways
- 42:03Q&A
related talks
46mFlaky, Fragile, and Forgotten: The Fall of a Test Automation Project
24mWHY ARE WE FAILING WITH TEST AUTOMATION?
32mLiving on Crotches or UI Automation Antipatterns
18mEffective Test Automation Framework Design
33mIntentional and Unintentional Compromises in Test Automation
24mA Comedy of Errors
21mThe Essential Pillars of Automation Testing for Success
52mHow to win with automation and influence people