Member-only story
Why do E2E Test Automation Attempts Repeatedly Fail Quickly at Software Companies? Part 1: The Hard Truth
Given the facts presented, it is inexcusable.
In this series:
- Part 1: The Hard Truth
- Part 2: The Whys *
I start with a quote from a world authority in Software Development and Agile:
“Automated testing through the GUI is intuitive, seductive, and almost always wrong!” — Robert C. Martin, co-author of the Agile Manifesto, on his blog (in 2009)
And, one by the author of “How we test software at Microsoft” book.
“95% of the time, 95% of test engineers will write bad GUI automation just because it’s a very difficult thing to do correctly”.
- this interview from Microsoft Test Guru Alan Page (2015)
Also, check out a great story told by Michael Feathers (renowned agile expert and the author of ‘Working Effectively with Legacy Code’) in 2009.
One veteran manual tester once told me, “This is the fourth time this company (large, 500+ IT staff) attempted to implement E2E Test Automation. Every time, people started with excitement; Then very quickly, no one was not interested in it any more, until the next time”.
