Practice makes man perfect – so goes the old adage. This is even more true for tests. While there could be few scripts to be executed on-demand for certain situations, as a rule of thumb attempt should be made to include automation test scripts with a continuous integration system. If there is no continuous integration system in place, it is absolutely a great idea to invest time and energy in creating one!
A good frequency of test execution helps in quickly establishing bad-builds when an error occurs. Comparing the test reports of successive runs, one can quickly ascertain when a test case first failed. This can save tremendous amount of time otherwise wasted in tracking the source of bugs.
Test results as Execution Log and Trace
As software ages, new features are introduced and sometimes these could break existing functionality. A daily build integration of test scripts preempts such avoidable errors. A test execution report with all “greens