Sign Up

Sign Up to our QA Community questions and Answers Engine to ask questions, answer people's questions, and connect with other people.

Sign In

Login to our QA Community questions & Answers Engine to ask questions answer people's questions & connect with other people.

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Sorry, you do not have a permission to ask a question, You must login to ask question.

Test Automation Feasibility Study Checklist:

Hey, Techie’s/Pal’s are you planning to start automation for an application? Then do not pick a tool randomly and then test an application. Later, if you have come to know the tool which was selected to automate is not feasible, and then you might be losing precious time and Money.

Here is a great way to do it: Yes, you got it right, it is the feasibility study on tools by considering the below checklist.

Aren’t you excited to know about it more, here you go: The checklist for any automation tool.

  1. The nature of the application: First, we need to know for which application we want to automate like is it Web, Mobile, Desktop or API. If there are more than one applications, then we need to pick the right tool which supports all these applications.
  2. Client requirement:  There are two types of clients in the industry 1) one who is having good Knowledge About Testing and automation tools, he can quickly identify the right tool and programming language to be used to automate. So directly, you can go to step 4 of checklist no four and do the feasibility study. 2) The Client who does not have any knowledge of automation, he informs you to pick the right tool to automate. While choosing the tool, you should also consider the financial budget of the Client. Usually, The Client having a minimal budget opts for open source tools(like Selenium, Katalon Studio, Cypress, WebdriverIO), if the Client does not have a stipulated budget, we can suggest the best commercial tool(Like QTP, Test Complete).        
  3. Study of Application in which Technology it was built: The web applications, which are built-in Technology like PHP, React having the webpages has some common attributes like ID, name, and value for HTML elements for locating. However, Pages built through Angular extends HTML and assigns new attributes called directives which create dynamic HTML content, so tools other than protractor cannot identify those elements, so we use protractor tool.
  4. Locators Identification: Open the application and check If your able to locate all the elements through inspect element option present in the browser, if you are not able to identify the locators then the application is not feasible for automation.
  5. Tool selection: Before opting for open source tools, make sure that there are enough supporting community and blogs so that if there are any queries in a tool, then it can be answered/resolved quickly. If it is a commercial tool, then make sure that the company is providing support round the clock.
  6. Browser compatibility: There are tools which do not support all the browsers, so before picking the tool check tool if it is supporting the browser which you require.
  7. Skillset:  After selecting the tool, you need to know in which development language it supports you to automate the application(like Java, JavaScript, Python, C-Sharp). Check whether your well versed with that language, if yes, then you can go ahead, but if otherwise, you need to gear up knowledge in that language.
  8. Integration Support: You should also check that tool supports to integrate with tools like Continuous Integration(like Jenkins) and Version Control(like Git). If it is an open-source tool, check your framework should be compatible to integrate with reporting tools(like Extent Report), bug tracking tool (like Jira, HP ALM).
  9. Do Sample Test: Pick any two simple test cases and try to automate with that tool, and if the tool is working fine, then go ahead and start the automation.

Hope you have got a good insight on the checklist for any automation tool, Please feel free to ask your queries [email protected]

 

3 Comments

  1. Good one !!!!!! Even we can add a point differentiating the commercial tools vs Open source !!! Few commercial tool doesn’t support all features for example multi window tasks !!!!! It would be difficult to access the windows!!!

Leave a comment