Image credit: https://unsplash.com/photos/U3sOwViXhkY

When to automate?

Alexey Sotskov
Sep 30, 2018 · 3 min read

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.


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.


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.


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.


Conclusion

As everywhere, there’s no a silver-bullet solution. And the answer on everything is: “it depends”.


Practical Software Testing

Only things that really matter in Software Testing

Alexey Sotskov

Written by

10+ years in Quality Assurance. I write about practical and effective techniques that help me and my colleagues in everyday software testing.

Practical Software Testing

Only things that really matter in Software Testing