Setting test runner options for a test case

Use the ZUnit category in the property group editor to set options for running an executable file or load library as a ZUnit test case.

1. In the property group editor, select the Category tab and click z/OS Automated Unit Testing Framework (ZUnit).
   A ZUnit tab is added to the property group editor.
2. Select the ZUnit tab.
3. Select Procedures and Steps.
   The Procedures and Steps page opens. For general information about the Procedures and Steps pages, see Setting options for procedures and steps.
4. To set options for the AZUZUNIT procedure:
   1. Expand the AZUZUNIT procedure and select the RUNNER step.
      The Runner Step Options area opens.
   2. Set options for the RUNNER step:

      Check Remote Locations: Verifies the data sets or folders that are specified in the Runner configuration destination container and Runner result destination container fields. The data sets or folders must exist on the remote system and you must have write access to them.

      Specify runner continuation settings: The runner continuation settings determine how the test runner operates under failure or error conditions. When a condition is selected, the test runner continues operating under that condition. When it is cleared, the test runner stops under that condition. If the Continue if test fails condition is selected, for example, then the test runner continues operating when a test fails; if the condition is cleared, then the test runner stops when a test fails.

      Runner configuration destination container: Specify an MVS™ data set or z/OS UNIX folder to store generated runner configuration files. ZUnit generates the runner configuration file and uploads it to this location when you run a test case. You can specify one of the following containers:

      • A z/OS UNIX folder on a remote z/OS system. You must have write access to the folder.
      • A partitioned data set on a remote system. The data set must have a record format of VB or VBA.

      The data set or folder must exist on the remote system and you must have write access to it.

      Runner result destination container: specify an MVS data set or z/OS UNIX folder for generated runner result files. ZUnit generates the runner result file in this location and downloads it to the client when the test runner runs successfully. You can specify one of the following containers:

      • A z/OS UNIX folder on a remote z/OS system. You must have write access to the folder.
      • A partitioned data set on a remote system. The data set must have a record format of VB or VBA.

      The data set or folder must exist on the remote system and you must have write access to it.

      Enable runner trace output: Select this option to enable tracing for the test runner.

      Additional JCL: Use this field to specify your own JCL. More data definitions (DD cards) can be specified here. The contents of this field are echoed at the end of the step. You must specify syntactically correct JCL.

5. To set options for the BZUPPLAY procedure:
   1. Expand the BZUPPLAY procedure and select the REPLAY step.
      The Dynamic Runner Step Option area opens.
   2. Set options for the REPLAY step:

      Check Remote Locations: Verifies the data sets or folders that are specified in the Runner configuration destination container and Runner result destination container fields. The data sets or folders must exist on the remote system and you must have write access to them.

      Specify runner continuation settings: The runner continuation settings determine how the test runner operates under failure or error conditions. When a condition is selected, the test runner continues operating under that condition. When it is cleared, the test runner stops under that condition. If the Continue if test fails condition is selected, for example, then the test runner continues operating when a test fails; if the condition is cleared, then the test runner stops when a test fails.

      Dynamic runner configuration destination container: Specify an MVS data set or z/OS UNIX folder to store generated runner configuration files. ZUnit generates the runner configuration file and uploads it to this location when you run a test case. You can specify one of the following containers:

      • A z/OS UNIX folder on a remote z/OS system. You must have write access to the folder.
      • A partitioned data set on a remote system. The data set must have a record format of VB or VBA.

      The data set or folder must exist on the remote system and you must have write access to it.

      Dynamic runner result destination container: specify an MVS data set or z/OS UNIX folder for generated runner result files. ZUnit generates the runner result file in this location and downloads it to the client when the test runner runs successfully. You can specify one of the following containers:

      • A z/OS UNIX folder on a remote z/OS system. You must have write access to the folder.
      • A partitioned data set on a remote system. The data set must have a record format of VB or VBA.

      The data set or folder must exist on the remote system and you must have write access to it.

      Enable runner trace output: Select this option to enable tracing for the test runner.

      Additional JCL: Use this field to specify your own JCL. More data definitions (DD cards) can be specified here. The contents of this field are echoed at the end of the step. You must specify syntactically correct JCL.

6. To add user or global variables for JCL substitution, click JCL Substitution.
   The JCL Substitution page opens. For more information about using substitution variables, see JCL substitution.
7. Close the property group editor and save the property group.