How To Decide What Should Be Automated?

Image for post
Image for post

Over time, automated testing has increasingly become more popular as compared to traditional manual testing. An increasing number of quality assurance teams have started preferring the former to the latter because of a variety of benefits. However, automated testing, like everything else, comes with its own prospects and consequences.

Automating each and every test suite might not be feasible in some situations. Economic and technological constraints do not allow each and every test suite to be automated. Hence, the team needs to filter out the cases which should be automated.

Here we have listed some parameters which may prove beneficial for deciding whether you should automate the suite or not –

What Is Its Priority?

How Often Do You Need To Run It?

How Many Test Cases Have You Got To Deal With?

Are You Going To Execute More Than One Test Simultaneously?

Are You Trying To Perform Cross-Browser Testing?

What Is The Volume Of The Input Data?

How Urgently Do You Need The Report?

Image for post
Image for post

How Expert Is Your Team?

Does The Test Require User Involvement?

What Are Some Cases Where You Must Not Automate?

Thus, this was a quick guide to deciding whether you should automate a test suite or not. Although, the choice is completely at the tester’s disposal yet going by the rules of the game can ease your task a bit and give you better returns on investment in terms of time and money.

Wish to add something to the discussion? Comment in the section below!

Image for post
Image for post

Originally published at www.lambdatest.com on July 23, 2018.

Author: Suraj Kumar

Written by

Product Growth at @lambdatesting (www.lambdatest.com)

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store