Member-only story
An Unbelievable True Story: People’s Fixation on an Obviously Failed “Self-Created” Test Automation Framework
While it is common that management sticks with a wrong decision, it is rare to an insane degree!
This article is one of the Stories series.
Since I switched my day job from Programming to Test Automation 13 years ago, I have worked on many software projects as a contract test automation engineer, regardless of title (several testing conferences’ brochures listed me as one of the world’s leading test automation experts), as long as I could do hands-on work on automated test scripts. Also, I declined any management roles or work involved with many meetings (such as test automation committee on testing strategy or like).
While working on these projects, I wanted to
- prove my test automation formula works for all web apps.
(Affirmative) - broad my knowledge to cover tricky scenarios
(I am particularly interested in the websites that people claim an impossible mission to automate)
I worked like this for about six years and improved my test automation efficiency further. Because of these experiences, I could do test creation live for clients on the first meet. It may sound like bragging, but I am confident that I have been at least 10X more productive than any other senior test automation engineers I have personally met.
Along the way, I have encountered some unbelievable, quite frustrating at the time but interesting stories. I once heard “Life is about stories”, and to experience some unbelievable ones is an asset. Today, I will share one.
Table of Contents:
∘ Background:
∘ A Bad Self-Created Automation Framework
∘ The project’s Test Automation was already struggling
∘ I Skipped a trap to get into managing Continuous Testing
∘ The Project Gave up on the ‘framework’
∘ The Success
∘ Insane: Back to MadX again in Project A
∘ What were the reasons behind that apparently silly decision?
