Automated testing technique for 4690 OS terminal sales applications
Original Publication Date: 2000-Feb-01
Included in the Prior Art Database: 2003-Jun-19
Disclosed is a technique to automate the testing of 4690 OS terminal sales applications. The testing of terminal sales applications on the 4690 Operating System is highly interactive. The tester must interact with the application via a keyboard and scanner as well as other input devices. The technique described allows this testing effort to be automated such that the tester does not need to interact with the terminal sales application. The technique is to link code into the application, via user exits for example, that will capture the input sequences being entered by the tester during test case creation. The tester can enter his test transactions and then end his session. The output of the test case creation session is the input sequence file that was captured as well as the other input files from the test run (Item record files, personalization options, and other files that will be needed when the test case is automatically rerun). The TLOG (Transaction Summary Log) for the test run is also captured this becomes the expected result for the test case and will be compared to the TLOG from the rerun to verify the results of the rerun match the expected results. The Electronic Summary Journal file is also captured this is a disk file version of the Summary Journal print tape and contains the print lines for the items which were sold. This file can be used to debug the problem if the TLOG from the test case creation run does not match the TLOG from the rerun. A batch program can be used to automatically run the created test case on subsequent releases of the application to verify that the output TLOG matches the expected results TLOG. The batch program copies the input files from the created test case into the appropriate directories for the terminal sales application. The test code that was linked into the application reads the input sequence file and can send these input sequences to the terminal sales application instead of polling the input devices for input sequences. By reading the input sequences from file instead of polling the input devices we can automatically replay all the transactions that the tester ran during his test case creation step. After replaying all the transactions, the batch program invokes a TLOG comparison tool to verify that the TLOG from the rerun matches the expected TLOG.