‘Let robots do the work’ is the common phrase now floating on the technology floor. Test automation can be considered as robot of testing. Having test automation and achieving majority test coverage with it, is considered as best practise in agile methodologies. It helps to adopt continuous integration(CI) and continuous deployment(CD) process. But pragmatically, does adding test automation always helps? Does it give the satisfied returns on investments made. When we look for opinions and experiences, we often hear mix responses. For some teams, it works like charm, some are struggling with it, some pushing it to just win the title that they have automated tests and rest don’t even bother about automation.
Test automation has always been highly miss-understood way of testing. The rational behind test automation is to help teams and ease testing. Reusability, accuracy, quicker, scalable, volume of tests and coverage, long term savings on time and resources are key potential benefits of having test automation.
So what leads to make it convoluted and miscellaneous?
Automated tests are indeed like robots but they don’t replace people at all. They are to help people and should always be considered to make the testing easy. They must be used to increase the quality of product by allowing team to focus more on intelligent testing. Automation should be enabler to test manually impractical scenarios and cover the large volume of platforms.
If used and build to its intended purpose, the automation will always help! Let us know your opinions in comments below.