AgileWay Test Automation Formula

A proven combination of frameworks and tools for achieving UI test automation success. I have been using the exact formula since 2011.

A repost of my old (still valid) article published on Medium 3 years ago.

Recently, a former colleague asked me for a successful test automation formula. This happened before; my default answer was to refer him to my book: “Practical Web Test Automation”, and advise him to do the exercises, and then apply them to work. I believe that the success of test automation depends on many attributes: knowledge, willingness to learn and be ready to change, test frameworks/tools, management support, .. etc. More importantly, do it hands-on from Day 1, and every workday onwards. There is no silver bullet.

When I put more thought into it this time, while I still hold the belief that successful test automation has many factors, I believe that there is a good pattern people can follow. A formula, based on my understanding, is a combination of components and processes that have been proven and others can copy and apply to use quickly. The universal applicability makes sense as our target (e.g. web apps) has not changed much.

An important attribute of the formula is completeness. To give an opposite example, I heard this in a meeting at a large financial company: “The DevOps team has been working on trying to run Micro Focus UFT tests in TeamCity for over 9 months. Can someone give us an estimation of the completion date?”. I didn’t remember the reply (from the DevOps team leader) to this, as I was shocked by the question. Apparently, the decision of the CI Server has not taken the UI tests into consideration! This means the people behind do not understand test automation or CI/CD at all, and they are still there.

By following a good formula, inexperienced engineers may avoid common mistakes, such as using Cypress, Gherkins, or JavaScript (as the scripting language).

Projects often make wrong choices on technologies for Test Automation

If a software project chose the wrong technology, correcting it was usually very hard (almost impossible). Reasons are:

• Management generally won’t admit the wrong decision and take responsibility.

• The tech lead will usually defend their wrong approach, and worse, sabotage correction efforts.

• Most IT engineers have never seen a single successful implementation of automated end-to-end testing.

Therefore, a good formula might not guarantee you success, it will prevent costly mistakes and keep you on the right track. Some talented and passionate engineers might be able to pull that off, or wise managers may seek help from a real Test Automation coach.

AgileWay Test Automation Formula

I have a good track record (15 years+) of doing successful Automated UI Testing, which is widely considered difficult. I have used the same technology /tools /practices successfully in many projects. I name it “AgileWay Test Automation Formula”: