Difference between Automated Testing and Having Automated Tests
Before drawing a comparison among these two visibly similar but fairly distinct terms let us understand the test automation process in totality.
We know that before executing the test cases, lot of groundwork related to setting up of several test prerequisites need to be done. This type of groundwork is usually termed as pre processing activity that is essentially done before the test execution can begin.
Similarly after the execution of the test cases, certain set of activities related to management of test result artifacts become essential. The management of such activities is termed as post processing.
Automation engineers usually go in for a common mechanism to automate all these pre & post processing activities. Performing these activities manually is extremely time consuming as well as prone to errors. Thus having an automation system for these in place, the new test cases just need to specify these tasks, instead of prescribing full details of their implementation.
We can’t say that we are doing automated testing if the tester has to be involved at regular intervals during a series of tests simply to restore data, etc. We can’t expect to have an unattended overnight testing if some sort of manual intervention is required.