Home | About Us | Products | Sales | Demos | Links | Support | Contact Us

PRODUCTS

Vermont Hightest
New Enhancements
Tour
Vermont Test
Test/Terminal
Vermont Views
UNIX
DOS
VSP Support
Year 2000

Vermont HighTest Plus Tour:
1 2 3 4 5 6 7 8 9 10

Page 4 — Playing a Script and the Log File

Before you start playback, you should verify that your playback options are set properly. These are detailed on Page 1 of the Tour. Make sure that the Playback Speed, Terminate on Failure commands and logging options are all set to meet your needs. From there, playing a script is as simple as clicking on the playback button on the toolbar. If a script is in the active window, HighTest will use that one, otherwise, it will prompt you for the name of the script to playback. As soon as playback starts, HighTest completely removes itself from the screen so it does not impact playback. It then starts sequencing through the commands, sending the keystrokes and mouse movements to the application, capturing screenshots, window information and file contents as specified in the script, and performing comparisons in real-time during playback so a failure in any command will have the ability to control the flow of the script, or cause the script to terminate immediately.

In the event that the playback is suspended due to a Terminate on Failure condition, a Pause() in the script, or the tester pressing the Suspend Hotkey, HighTest will restore itself to the screen and display the script with the current line highlighted. You may then either start debugging the script (see Page 7 of the Tour), end playback altogether or continue with playback from where it was suspended. At the end of the script, HighTest will restore itself to the screen and if the log file is set to automatically open, will display the log file as in the example below:

Because you can specify which commands will be logged, not all commands will necessarily be in the log file. For each command that is logged, you will see the command, all of the parameters for the command and the result of the action. In the example above, there is one failure noted in the log file - the CompareScreen() command. You will then want to look at the reference and playback images that are stored in the HighTest database to determine why the images did not match (see Page 5 of the Tour).

If you have selected Append to Log in the log preferences, you will see multiple runs of the script within one log file and will allow you to see any differences between the two runs of the script.

Tour: 1 2 3 4 5 6 7 8 9 10