When to Run Automation Testing

Testers generally use their common sense in deciding whether to use automation testing or not. If they are to execute the test case once or twice, automation would be expensive here. They will then carry out a manual testing. But it is easier to say “use your common sense” than doing it. The pros and cons of automation and manual testing should be discussed to determine when and how to automate.As stated, if the test will only run coding milestones once or twice, then a manual test is recommended since it is less costly compared to running automation. Manual testing also enables testers to carry out more ad-hoc or random testing. Many testers claim that they find more bugs via ad-hoc compared to when the test is done through automation. In addition, if testers spend more time playing with the feature, there are greater odds to find actual user bugs. However, manual testing consumes a lot of time, and every time there is a new build, testers need to rerun all necessary tests. This would eventually become very tiresome and mundane.You may want to resort to automation if you need to run tests repeatedly. Automation will give you an advantage because it has the ability to automate against codes that always change to catch regressions on time. It will also enable you to run tests in mainstream situations to catch regressions. Moreover, automation helps in testing a complex test matrix. While manual tests must be run sequentially, you can run automated tests simultaneously on different machines.On the downside, automated tests will cost you more compared to running manual tests. In addition, configuring or writing the automate framework you use or writing test cases will cost you more initially compared to running manual tests. Another major drawback of automation is that you visual references cannot be automated. For instance, if you cannot distinguish the font color through the automation tool or code, then you should run the test manually.You may also want to consider other deciding factors. First, automation is dependent on the tools you are using. If those tools have any pitfalls, then it is better for you to run the test manually. You also need to have an idea whether the ROI (return on investment) is worth automating. You must also make sure that what you get in the end with automation is worth the money spent in putting into place and supporting the automation framework, the test cases, and the systems that run the tests.You must ask yourself the following question to decide whether running automated tests is appropriate for your case: Is the test case automatable? If it is automatable and costs a little, then you should go for automation. If it is automatable but will cost a lot, then you must think twice if automation is worth the investment.But what if the test case is not automatable? Then you need to reevaluate – will you run the test often? How much will it cost when the test is done manually? You must consider these questions before whether to run automation testing.