Run your test
In Navigate the application under test, you erased and retyped the port number. It's time now to make a slight edit to the script to cause it to use a different port so that it plays back against the second version of the application.
- In the Test Script view -- the center pane of the Functional Tester window
-- locate the line that edits the port number:
- Edit the line to type the number 24. Your line should now look like this:
Before you play back the script, check a couple of things:
- Verify that there are no terminal emulators open. Your script will open a terminal emulator session and you don't want it to get confused if multiple emulators are open.
- Verify that the Host Simulator is running. You can verify this by verifying the two Java applications are visible on your Windows launch bar.
To play back the script, click Run Functional Test Script
You will be prompted for the name of a log in which to store the results of the test. Functional Tester will use the name of the script as the default name for the test log. Click Finish to accept the default.
Now you can sit back and watch as Functional Tester repeats your test steps against the newer version of your application. Do not attempt to use the mouse or keyboard until Functional Tester finishes playback of the script.
When Functional Tester finishes, you should be presented with an HTML log of the test results. Again, this is similar to the logs you've already seen if you've tested Java, Web, or .NET applications with Functional Tester. The log records major events, such as the script and application launch and termination, as well as the status of all verification points. If you had any script failures or warnings, those would be logged here as well.
The left navigator frame gives you quick access to the most important parts of the log. You should note that there is one failure. One of your verification points has failed. Click [Field_16_63_text] failed in the Failures area of the left navigator frame. This will cause the log to scroll to the appropriate failure entry. To get more detail on this failure, click the View Results link. This brings up the Verification Point Comparator.
The Verification Point Comparator highlights in red the differences between the expected value and the actual results. Here you see that, although we clearly purchased 100 shares, the final real-time quote screen shows only 10 shares held in the account. Mission accomplished! Your simple regression test has exposed a regression in the application. This functionality worked in version 1, but fails in version 2. It's time to file a defect report.