1. INTRODUCTION
This document details the Automation tool selection strategy. It must be ensured that the application or technology in hand is actually supported by the automation tool we are going to select for automation. The entire process of tool evaluation can be broken down into three major phases.
· Requirement Gathering
· Tool Selection
· POC
1.1. Requirements Gathering
During the requirements gathering phase of tool evaluation automation engineer will list out the requirements for the automation tool. Some of the items that will guide automation engineer for requirements gathering are
· Compatibility issues
· Tool audience
· Licensing Cost
· Testing requirements
1.1.1. Compatibility Issues
Testing tool should be compatible with
· The operating systems <Project Name> supports
· The development environments used to create <Project Name>
· Third party tools which used in the application
1.1.2. Tool Audience
The skills of people involved in test automation and that of the people who use the automation scripts is another important criterion for the test tool evaluation process. The benefits obtained through automation boils down to how effectively the tool is being put to use.
· Verify the automation team and other members who will use scripts are familiar with the tool.
· In case if not familiar, then how much effort required to be familiar with the tool.
1.1.3. Licensing Cost
It is very important phase of the tool selection. It should be known that how much cost can be bearded by the management.
1.1.4. Testing Requirements
What type of testing problem needs to be addressed by the testing tool? Below are few points that can help in determining.
· Manual testing problems
· Time constraints when implementing small changes in the system
· Shorter regression testing timeframes
· Test data setup
· Defect tracking
· Increased test coverage
· Increased efficiency of the testing process
1.2. Tool Selection
The second step in test automation tool evaluation is the selection of tools. While selecting tools it is important to remember that no single tool will satisfy all the requirements. The tool that meets most of the evaluation criteria should be chosen after discussion with stakeholders. Based on the tools limitations with respect to requirements, the automation activities must be planned. All tools that meet most of the evaluation criteria can considered for evaluation. When many tools are found to satisfy the evaluation criteria, further analysis of tools should be done. Ÿ
· Mandatory features: These are the features that are essential to accomplish the goal in meeting requirements within the constraints
· Desirable features: These are features that will distinguish the best tools from the others
· Irrelevant features: Features that are not important and will not provide any real benefit
1.2.1. Selected Tool
<Selected Automation Tool>
1.3. POC (Proof of Concept)
· Key scenarios of the application will be Identified and will be executed on selected automation tool to ensure that they are supported by the selected automation tool
· It will be assured that the selected tool supports third party tools, if any third party tool used in application. In case if tool does not support the third party tool that will be mentioned as “out-of-scope” for automation.
· Automation team will work with development team in design phase to assure that objects properties are properly exposed
· After complete evaluation of the tool a report will be designed and published with the team.
Post a Comment