Tracked field, Spell Check, Markup and Validation Rule support is currently in TestDrive only and these Scripts cannot be amended or played back natively.

1 Key option 10 against the Test Case where the Script you are about to play back is stored.
2 Select the correct Script from the list.
3 On the Script Options panel select the options required (refer to the earlier section on Script Options for more information). Any changes made here will affect this run only.

4 On the Script Initiation panel the following options are available.

Run Description Optional field which appears on the Sub Run display if entered.
Reference Optional user controlled text which is displayed by pressing F7 on Test Run Details in results. It can be used for any purpose, for example to group multiple runs together via a single work request number.
Run Mode This is always used in preference to the run mode entered against the Test Case.
Screen Delay Playback delay in one second increments between the keystrokes being entered into the display and the next screen appearing.
Keystroke Delay Playback delay in one second increments between the screen first appearing and the keystrokes being played into it.
Pause Mode Script will be paused after each screen is displayed and the option is provided to view the screen results captured so far. Enter must be pressed for playback to continue.
Variable Data Set Specify a public variable data set to be used as an alternative to the local or public set stored against the script. This option is only available for scripts whose variable data was created using TestDrive or Original Software Manager. The user must ensure that the variable data field names in the Data Set match those required by the script.

5 Select any Test Items which are to be looked at for this test run. See the Select Test Items section in Testing for more details.

6 Playback will begin in a new session created by TestBench, and automatically stops when the first screen is displayed. It is compared to the first expected screen in the Script and a message in the Script Paused window indicates if any differences have been found. Press F7 to display the screens with any differences highlighted. Press F9 to proceed if this is the correct starting point for the Script – it is possible to proceed even if errors have been found on this first screen. Alternatively, press F3 to cancel the run.
7 The Script will now run in the new session and the results for each screen will be captured. When the Script has finished the Test Run Details screen will be displayed so that Results can be viewed.
NOTE: If an error is received during the playback of an integrated Script which causes a TestBench window to be displayed, for example a field is missing from the screen that TestBench is trying to key data into, the User must press F3. TestBench will then attempt to send a System Request to the session and close it down, ending the test. However, if the program under test is a request handling program, this will not work and the test will not close down correctly. User intervention is required in this situation.
Play_IT Command
This command interface enables a Script to be replayed immediately for fast start test execution. If the command Play_IT is keyed and Enter pressed, a selection screen will be displayed for each piece of information that is required by the command, ie. Project, Test Case and Script Name. Once each of these has been selected the following screen will be displayed and the other parameters can be keyed as required. Pressing F3 at any time from the selection screens will also cause this screen to be displayed, with as many fields filled in as have been selected up to that point.

Project The name of the Project in which the Test Case exists.

Test Case The name of the Test Case against which the Script is stored.

Script Name The name of the Script to be replayed. This field is case sensitive.

Run Description Optional field which appears on the Sub Run display if entered.

Run Reference Optional user controlled text which is displayed by pressing F7 on Test Run Details in results. It can be used for any purpose, for example to group multiple runs together via a single work request number.

Device Type If submitting the request to batch the device type must also be specified (F4 to prompt).

Bypass Pre-check Warnings
When a Test Case which calls a program directly is executed the Level ID of the program is checked to ensure that it has not changed since the Test Case was created. If it has changed, a message is displayed and you are forced into Test Case Maintenance to re-confirm the parameter definitions for the program. If this occurs when running a Test Case using the Play_IT command it will prevent the Test Case from executing and therefore the Script will not run. If you can be certain that the calling parameters for the program have not changed then this level check can be bypassed with this option.

Bypass First Screen Check
When a Script is re-played, by default it will pause on the first screen of the application under test and ensure that the application screen and the first screen in the Script are the same. The User can then press F9 to proceed with playback or F3 to end the test. If, for example, this Script is only one of many that are being re-played as part of an Action Map, it may be undesirable for each Script to halt on the first screen and require User intervention. When this option is set to *YES, this confirmation screen will not be shown and the Script will automatically continue with playback once the first screen appears.
Variable Data Set Specify a public variable data set to be used as an alternative to the local or public set stored against the script. This option is only available for scripts whose variable data was created using TestDrive or Original Software Manager. The user must ensure that the variable data field names in the Data Set match those required by the script.

A completion message will be written which can be monitored for to determine if any warning messages were generated and therefore whether or not the test ran successfully.

TBR0281 No warning messages
TBR0282 Warning messages

The Play_IT command could therefore be submitted as part of a change management process to ensure that the program works correctly. The user could monitor for the success message and if it was received the program could be promoted. Alternatively the Test Run API can be used to interrogate the results of a particular Test Run to provide more detailed information about the success of a test. See specific section in Results chapter for more information.