When implementing test automation there are several things to consider - which tests should we automate? which tool is the right tool? can the initial investment of time and effort be justified? Read on to get these questions answered and to get off to a good start with test automation.
It’s a common challenge that steep learning curves make it difficult to evaluate automation tools within a reasonable time frame. This can cause the evaluation to drag out and in the worst cases, automation projects are tanked altogether.
This post outlines some simple steps for evaluating and implementing automation tools, letting you get started with test automation in a matter of weeks, not months.
When choosing an automation tool, whether it is for automating tests or business processes, it is important to set up some criteria for evaluating whether the tool is the right fit for your organization.
It is our experience that to find the right automation tool there needs to be a fit in the following three areas:
The evaluation phase should not have to take more than five days. If it takes much longer to do an immediate evaluation of a tool, it might be because the tool brings with it an unnecessary amount of complexity.
Define the technology that you are looking to automate, and then find out if the automation tool in question supports that technology. In most cases, you can place it in one of the following main categories:
Web-based technology or mobile web application
Citrix or other virtual desktop-based technology
Start by outlining two or three flows that you want to automate. We recommend identifying some common processes that are often repeated and which, if automated, would bring about significant efficiency gains.Then use these cases for evaluating a tool’s user-friendliness; how easy is it to build these flows as automation cases with the respective tool?
To make sure that an automation tool is a good fit for your organization, you should distribute the relevant documentation and materials related to the tool to the respective stakeholders:
Once the alternatives have been evaluated, and you’ve chosen the tool to proceed with, it’s time to roll it out in your organization. Implementation consists of two main activities: Training and deployment.
Ideally, the automation tool vendor should provide both a training program and readily available training materials designed to facilitate an advanced and fast internal adoption of the tool. The goal of a training program should be to enable participants to implement complete automation within their business domain.
A training program could look like this:
Day 1 – Onsite:
Days 2-4 – Online:
Day 5 – Onsite:
The purpose of this phase is to ensure that the components of the automation tool are installed properly in a “best fit” deployment from the get-go and that scheduled runs of automation flows work as intended.
The deployment phase consists of the following deliverables: