A “Full Stack Developer” Blames ‘Chrome Releases’ for Unreliable E2E Test Execution, Absurd!
A typical fake automated tester blames everything but his/her capability.
My recent article, “Why Software Testing is Not Effective in Most Software Teams?” has quickly become one of my most popular pieces.
One reader (who claims to be a “Full Stack developer”. I refer to this person as AB) left this comment for this article.
“It seems every new release of Chrome breaks our tests in a different way. They don’t save you time if they won’t reliably run, and if you have to do a major repair to your tests every couple of weeks, you’re not writing new ones.” — AB
AB contributes to the repeatedly unreliable execution due to “every new release of Chrome”. This is absurd; I heard it for the first time in over 14 years of test automation consulting/coaching. I will explain it a bit later. (By the way, long-time readers know that I rarely write an article about readers’ comments. But this one has some educational value)
I responded to the comment, trying to be nice and not point out the absolute wrongness in AB’s statement.
“If you run the whole End-to-end UI Suite every day, the maintenance issues don’t get added up. Chrome…
