What Are the Challenges in Implementing Test Automation?

Ref: my Quora answer here

Despite various benefits of an automation framework, jumping to test automation is not simple. IMO, there are generally 3 challenges.

1. Upfront costs

When it comes to adopting a test automation framework, the first and foremost obstacle would be the upfront cost, whether it’s training cost, tooling cost, configuring cost, automating cost, etc. The following picture illustrates the sum cost of test automation over time.

Most test teams give up when being faced with this daunting deterrent and satisficingly return to manual testing. However, the good news is if your team persists through the initial pain to achieve a critical mass of automated tests, your investment will pay off handsomely.

2. Ain’t nobody got time for that

When asked, most of the time a team would answer “we are overly swamped; we cannot take on more tasks, especially this automation thing”. This scenario is typical when a test team is already behind schedule. All they want is to focus on completing the manual testing work at hand to keep up with the deadlines. They don’t have too much time and energy left to look elsewhere.

However, that’s a great embodiment of the chicken and egg paradox. The longer you postpone test automation, the more overwhelmed by manual testing you will be. The days that your team can keep dragging it on are numbered. Hence, whether people like it or not, we must eventually break out of this vicious cycle once and for all. Of course, sooner is better. And besides, looking at test automation in a different angle, the team will realize that “just another poison” is actually the antidote.

3. It isn’t worth it

Many testers compare automating tests with trying to hit a moving target. Just when you think you got it in place, it changes. The requirements tend to take different shapes over time in sync with user needs and business contexts. Therefore, it’s highly recommended that you choose tests to automate wisely based on projected ROI. Rule of thumb: an automated test typically pays for itself after approximately 3 regression runs. If you don’t have to execute a test repeatedly, don’t bother automating it. Check out my listing of tests you should automate here.

4. Organization challenges

Changing is always hard from the organizational standpoint. Where does this automation framework along with the automation engineers fit in? Will it interrupt our day-to-day operations? As a manual tester, will I lose my significance?

As the advocate for test automation, you can deal with those concerns as follows:

• Provide definitive goals and a clear step-by-step timeline to effectively persuade the team. Admittedly, new roles are introduced and existing roles are modified but nobody is being left behind. Everyone can bring their value to the table after all.
• Wisely allocating and effectively managing resources are crucial in the execution step. It means you have to help people understand clearly what is expected from them and how they can adapt to the new work processes.