Software Test Automation

Software testing is an essential, yet time-consuming, and expensive activity. Therefore, automation of any aspect of software test engineering can reduce testing time and, in the long-run, reduce costs for the testing activity. While there are many research directions in testing automation, from theory through application, the main focus of this special issue is on partially or fully validated tools, techniques, and experiences.

1.  Regression automation

• create and run Test case and inspect the output results

• if the program fails, report a bug and try again later

• if the program passes the test, save the resulting outputs

• in future tests, run the program and compare the output to the saved results

• report an exception whenever the current output and the saved output don’t match

2. GUI Automation

• GUI test tools must be tuned to the product and the environment
• Maintainability is a key issue because our main payback is usually in the next release, not this one.

Graphical user interface testing. A testing framework that generates user interface events such as keystrokes and mouse clicks, and observes the changes that result in the user interface, to validate that the observable behavior of the program is correct.