Guidelines for Selecting Test Cases for Automation

Repeated Tests

If a test is run repeatedly, it should be automated to save time and effort, delivering faster and more accurate results, especially when future frequent execution is expected.

High‑Difficulty Test Cases

Test cases that are prone to human error or are hard to perform manually should be prioritized for automation, particularly when they involve high risk.

Main‑Flow Test Cases

Automating the main workflow of an application is a best practice to eliminate human mistakes, ensuring safety and speed, and protecting the overall project.

Broad‑Scope Test Cases

Scenarios requiring large amounts of data or conditions, and those with a high chance of manual error, are well‑suited for automation, such as tests that involve filling many forms.

Cost‑Benefit Evaluation

Assess the time needed for automation versus manual testing; if automation requires disproportionate effort, it may not be worthwhile.

Three Golden Tests

Automation should always include regression, smoke, and sanity tests, as each internal or release version of the application needs to be verified.

Ask “Why?”

Never automate simply because you can; the benefits must outweigh the costs, and the answer to “why automate?” should never be “because I can.”

Complex Cases

Test cases with many pre‑conditions are prime candidates for automation to save time, even if only simple scripts are needed for functional testing.

Performance Tests

Automate performance testing such as load and stress tests, which are difficult to achieve manually.

Long‑Running Tests

Tests that run for extended periods (minutes to hours) should be automated.