Penicillin is not for every illness. So does Test Automation — Part I
Test Automation has become an indispensable player in software testing over the last decade that promises efficiency, accuracy, and speed. However, like any other tool, its effectiveness solely depends on the context it is used. Understanding when test automation offers a return on investment and when it does not is essential for making decisions about its implementation. Test automation can help to reduce testing time, increase test coverage, and reduce development costs. However, it requires significant effort to set up the tests and to maintain them, and may not be suitable for certain projects.
This has two parts and as the first article let’s focus on where automation is well suited with some practical examples.
Repetitive Tasks: Automation is designed and well-suited to execute repetitive, routine tests. Test cases or scenarios that need to perform the same set of actions repetitively; for instance regression testing, can be efficiently automated, saving time and effort. Regressions executed via automation will offer faster feedback and leave room for testers to focus on other tasks that require human intuitiveness.
Assume you have an e-commerce application with the below tests to be verified in your regression.
- Verify the search is working…
