Member-only story

E2E Test Automation Anti-Pattern: Developer-Focused Approach. Part 3: Most Developers Lack Proficiency in Test Automation

It’s like an Uber driver attempting to compete in a Formula One race: they might be able to start, but there’s a high chance they won’t be able to finish it properly.

Zhimin Zhan
7 min readJul 15, 2024

This is an article in the E2E Test Automation Anti-Pattern series.

Many software developers probably don’t like the title of this article, as software developers tend to think “automated testing is easy”, which was what I used to think before 2005.

Disclaimer: as a Micro-ISV, I do programming as well as testing (automated).

Let’s start with some quotes from several software gurus.

Quotes from Renowned Software Figures

“In my experience, great developers do not always make great testers, but great testers (who also have strong design skills) can make great developers. It’s a mindset and a passion. … They are gold”.
- Patrick Copeland, Google Senior Engineering Director, in an interview (2010)

“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), author of “How we test software at Microsoft

“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)

“Testing is harder than developing. If you want to have good testing you need to put your best people in testing.”
- Gerald Weinberg, software legend, in a podcast (2018)
(current generation of programmers might not heard of Gerald Weinberg, check out the a tweet by DHH on 2023–12–27: “Nobody taught me more about how to do that than the late, great…

--

--

Zhimin Zhan
Zhimin Zhan

Written by Zhimin Zhan

Test automation & CT coach, author, speaker and award-winning software developer. Help teams succeed with Agile/DevOps by implementing real Continuous Testing.

No responses yet

Write a response