Why Software Testing is Not Effective in Most Software Teams?

Advice: Adopt E2E (via UI) Test Automation.

Zhimin Zhan
7 min readFeb 5, 2024

--

Update (2024–02–22): My new article, “Three Types of Efforts in E2E (UI) Test Automation Clarified”, may help some readers understand why most E2E test automation attempts fail.

Today, I shared a Reddit Meme, “theRealtester”, with my thoughts on LinkedIn.

https://www.reddit.com/r/ProgrammerHumor/comments/1aiq7tw/therealtester/, with 4.5K likes

Within a few hours, my post received 100+ likes.

Interestingly, most of the comments are related to testing environments, such as:

“that’s why UAT it’s so important and a good practice in every agile team”
“The problem is different env coverage are not taken to the account by testers.”
“Few Reasons: -Different Environment , Scope of testing in this sprint,Timebox.
-If we give free hand to testers without timebox then they can find many bugs in short duration.”

That’s off the track. Then I realized two things:

  • Most people just read the Meme (the image), not my words.
  • They seem related more to manual testing, neglecting Test Automation.

I decided to write an article focusing on the E2E (via UI) Test Automation aspect.

Table of Contents:
·
Manual Testing will miss many defects, of course
·
Software Testing is mostly not Effective
·
Spending a lot of time on Test Design is mostly a waste
·
Simple Solution to Test Design
·
How to Design Automated Tests Efficiently?

Manual Testing will miss many defects, of course

It is so obvious that I will just list some quotes from world-renowned authorities.

The majority of software issues are regression-related.

--

--

Zhimin Zhan

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