Making a Wrong Framework/Tool Decision in Web Test Automation is Inexcusable — Yet It Happens a Lot.

Lacking fundamental knowledge of web test automation, which has remained largely unchanged for over two decades. IT executives, it’s time to put an end to this nonsense.

Non-Medium Members, you can read this article free on Substack.

Web Test Automation means Objective, Fast and Instant. Most people can understand The “Objective” and “Fast”. But why “Instant”?

Core Web technologies have barely changed over two decades.

“If a test automation engineer has ever done one successful test automation, the knowledge, skills and practices can be directly applied to future ones. It is like “Bike Riding”, once you really master it, you prove it instantly. “ — Zhimin Zhan

Once pointed out (as seen above), it should be quite obvious, shouldn’t it? Web test automation should be results-driven, right? Yet, in reality, failed attempts at web test automation are everywhere.

Despite all the fancy titles such as Test Automation Architect, Principal SDET, and Senior Test Automation Engineers, few self-labelled software projects achieve effective and visible end-to-end (UI) test automation in daily use.