1. Test Cases Automation Criterias (Tech)
Criteria #1.1: Test cases used for regression testing.
Regression testing means, that you verify some functionality that must not be broken with new release. I.e., you want to “cement” that “old” functionality. And you can do “cementing” with auto-tests.
But don’t hurry up. As test cases are borned not equal, they have assigned priorities: P0, P1, P2… or Critical, High, Medium… etc.
That’s why, obviously, P0 (or Critical) test cases used in Regression testing — are the best candidates for automation.
Criteria #1.2: Non-functional tests, that are hard or impossible to execute manually.
This is all kinds of Performance tests: Stress testing, Load testing, etc. They are hard or even impossible to execute manually. It is often a good idea to automate such test cases.
Even if you, especially with Continuous Integration and Continuous Delivery (CI/CD) process, deploy some servers to Production (for beta users) and monitor Performance metrics degradation to evaluate your software without auto-tests on real users, you still don’t use “manual” testing for that. You “automated” that testing with CI/CD process + monitoring.
So, that’s why these non-functional tests are also the best candidates for test-cases automation.
Criteria #1.3: It is easier to create them automated right from the beginning.
Sometimes (or often, “for whom how”) there are cases when it is so easy to write test cases automated right from the scratch, — so you don’t need to write and execute them as manual.
Sometimes (or often, again) there are cases when it is very difficult for manual testing to emulate some condition. But with auto-test cases it could be done easily!
These test cases also the best candidates for automation.
2. Test Cases Automation Criterias (Business)
Criteria #2.1: To look better in investors eyes
Some investors look at the company growth (number of employees) — that’s why you can hire not so expensive automation QA Engineers and just let them automate anything.
Some investors like to play Boolshit Bingo game and they are attracted by the phrases like: “100% test automation coverage”, “Continuous Integration”, “Continuous Delivery”, “Cloud Based”, “Artificial Intelligence”, “Big Data”, “Data Lake”. Boolshit! Bingo! :) That’s why you hire all these beautiful people to win such kind of investors.
Some investors look at the invoice growth. And you can afford this with automation appliance as well. That’s why you start your DevOPS and automation QA processes.
To understand this more, take a look at this:
As everywhere, there’s no a silver-bullet solution. And the answer on everything is: “it depends”.
That’s why always there are some criterias that help you to define the best (least evil, actually) solution(s) for your problem.
I’ve shared 3 classic tech criterias for test cases automation, that I know and 1 business one. If you have more, please, share them in comments below!
P.S.: I hope you liked an article and found it useful. If so, please, don’t hesitate to give it some claps so more people could read it!