This is the screen shown at the start of a Test run to confirm the options you wish to have in force at the time of the run. See the ‘Native’ Record and Playback and TestDrive sections for information on initiating scripts as part of a test.

Run Description Relates to this particular Test Run only and is displayed in Test Case Results.

Reference 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 work request number.

Job date options A Test Case can be set up to execute under a different job date, and a Process can be re-executed by advancing the job date by a specified interval(s). These options can be made inactive for this run by keying choice 2 in this field, in which case the standard job date is used. The override of this option can be prevented in System Values.

Call Interceptions If the Test Case is set up to intercept a call to a lower level program, this call can temporarily be made inactive for the duration of this test run. The override of this option can be prevented in System Values.

Function Keys

F7 – Edit Test Case Prior to starting this test run, Test Case information can be changed by pressing F7. These changes are stored and will apply the next time the Test is executed.

NOTE: If any of the programs being called by the Test Case Processes have changed since the Test Case was defined, a message will be displayed on this screen. If you can be confident that the calling parameters have not changed then F8 can be pressed to bypass this warning which will not be displayed again. However, if the calling parameters may be different then press F7 to edit the Test Case and re-scan the program for parameter definitions.

Select Test Items
TestBench holds a testing check-list as Test Items. These are defined for each Test Case and at the initiation of a run you are prompted to select which of the items are to be looked at during this test run. These can include aspects of the testing which require human assessment as well as areas which TestBench will look at for you. Either during or at the completion of the test run, a pass or fail can be recorded against each item and new items can be added. Hence the Test Items provide a means of keeping track of the progress of a Test Case and identifying and reporting when it has been successfully completed.

Select Test Items Key 1 to select individual items from the list using roll/page to reach the end of the list. Alternatively, use F20 to select all items. Additional items that apply to this run only can be entered at the end of the list. You do not have to select any items to start a test run.
Test Run Pre-check Warnings
Prior to a test run starting, TestBench checks the objects according to the Pre-check Scope option in Test Case Maintenance that will be updated during the test and lists where these are to be found. If a file is not found or will not be protected this is indicated next to the file name. If data protection is not active (Test data = *LIBL in the Test Case set up) a warning is shown at the top of the screen that no objects will be protected.

If you expect all the files you use in a test to be protected, ensure that there are no messages in the above display to contradict this before continuing.

Option

1 – Include If an object has been excluded from data protection using option 2, this option will include it again.

2 – Exclude Exclude an object from data protection for this run only. This option cannot be used for manual references.

5 – Display References Check which programs access each listed object.

System Library Pre-Checker
During the execution of a test a temporary library is created that must reside above all other System, Product and User libraries. This ensures that the files designated for protection during the test run and any other objects copied by TestBench for the duration of the test are always higher in the library list than other copies of the same objects in the library list. If the use of the CHGSYSLIBL command is not allowed there is a flag on the System Values screen that must be set to ‘2’. If you do this there are several implications due to the fact that there will be no test run time library and therefore no objects can be copied into it. The following testing functionality cannot be used:-

• Data Protection. Environment protection only is allowed.
• Tracking submitted jobs on active processes.
• Program interception.
• Data Queue interception.
• RTVSYSVAL or OVRDBF interception.
• Testing of Group Jobs.

The following screen will be displayed after the Test Items and Pre-check Warnings screens if the Test Case is attempting to use any of the above functionality. Use F7 to modify the Test Case before continuing.

Accessing Test Items During a Test Run
When testing an interactive application in TestBench, by default the list of Test Items selected for the run can be accessed at any time by pressing the Escape or Attention key, unless this has been inactivated using the Test Case option or when recording a script using the ‘Native’ recording function when the Attention key is used for a different purpose. The status and comments can be updated as the test progresses, and any new items can be added. In addition, the text notes for the run can be entered, retrieved and amended. This enables additional information, such as explanations or diagnostics associated with a test to be captured and stored with the other test run details. The status, comments and notes can all be printed on the Test Run Report document produced by Report_IT. For more information about using the Notes editor, refer to that Chapter.

Pass/Fail Enter the status for the Test Item which can be either blank, Pass or Fail.

Function Keys

F14 – Run Notes Add any additional notes to the Test Run if the Comments field provides insufficient space.

F21 – Cmd Entry Access a command line.

F22 – User Exits Create additional User Exit commands during the Test Run.