Task: UnitTest

Description

This task executes IBM Test Accelerator for Z unit tests.
NOTE: This task requires a user jobCard to be provided.

Task dependency list

List of tasks that must execute before this task.

• File Analysis
• Language Tasks

Actions

• Filter the BUILD_SET for TAZ unit test configuration files.
• For each configuration file generate and submit a JCL job to execute the test case.
• Save the job output and report file of the test results to z/OS UNIX.

Syntax

- task: UnitTest
  comment: String # Message printed to stdout when the task begins executing.
  condition: Boolean # Boolean expression to optionally execute task. Default is true.
  variables: 
    - name: jobCard # Unit test JCL job card.
      value: String # Default NONE.
    - name: configSources # File patterns used to match files in the BUILD_SET as Unit Test configuration files. 
      value: String # Default is "**.bzucfg".
    - name: configDS # Partitioned dataset for configuration files.
      value: String # Default is "${HLQ}.BZU.BZUCFG".
    - name: configDSSpace # Space allocation for creating configDS. Use BPXWDYN syntax.
      value: String # Default is "cyl space(1,1)".
    - name: recordingDS # Partitioned dataset for recording files.
      value: String # Default is "${HLQ}.BZU.BZUPLAY".
    - name: recordingDSSpace # Space allocation for creating recordingDS. Use BPXWDYN syntax.
      value: String # Default is "cyl space(5.5)".
    - name: recordingSearch # The search path used to find the testcase recording source files on z/OS Unix.
      value: String # Default is "search:[SYSPLAY:]${WORKSPACE}/?path=${APP_DIR_NAME}/**.rec"
    - name: reportDS # Partitioned dataset for test report files.
      value: String # Default is "${HLQ}.BZU.BZURPT".
    - name: reportDSSpace # Space allocation for creating reportDS. Use BPXWDYN syntax.
      value: String # Default is "tracks space(200,40)".
    - name: testDS # Partitioned dataset containing the unit test load modules.
      value: String # Default is "${HLQ}.TEST.LOAD".
    - name: programDS # Partitioned dataset containing the program load modules.
      value: String # Default is "${HLQ}.LOAD".
    - name: userLibrary # Optional additional user dataset needed to execute tests.
      value: String # Default NONE.
    - name: jobParm # Unit test JCL PARM value.
      value: String # Default is "STOP=E,REPORT=XML"
    - name: useDebug # Flag to run test case in debug mode.
      value: Boolean # Default is false.
    - name: debugParm # Unit test debug JCL PARM value.  Concatenated to 'parm'.
      value: String # Default is "TEST(ERROR,,PROMPT,DBMDT:*)".
    - name: useCodeCoverage # Flag to activate code coverage.
      value: Boolean # Default is false.
    - name: codeCoverageHost # Code coverage host machine address.
      value: String # Default is NONE.
    - name: codeCoveragePort # Code coverage host machine port.
      value: String # Default is NONE.
    - name: codeCoverageOptions # Code coverage options.
      value: String # Default is NONE.
    - name: fileBuildRank # File associated variable used to control the execution order of test cases.
      value: Integer # Default value is NULL.
    - name: logEncoding # The file encoding of the JCL output log file.
      value: String # Default is "IBM-1047".
    - name: maxRC # Maximum JCL step return code to indicate a successful test case execution.
      value: Integer # Default is 4.
    - name: useHLQ # Since 3.0.2: Optional variable to override the default &SYSUID
      value: String # Default is &SYSUID
    - name: reportTag # Since 3.0.2: The file tag of the generated XML report. Changes tag, not encoding.
      value: String # Default is UTF-8

YAML variables

variables:
  - name: jobCard
    value: |-
      //USER1 JOB ,  
      // MSGCLASS=H,MSGLEVEL=(1,1),TIME=NOLIMIT,REGION=144M,COND=(16,LT)  

variables:
  - name: fileBuildRank
    value: 1
    forFiles:  # these test cases are executed first
      - **/tests/eps*.bzucfg

Build Context (advanced)

In addition to the YAML variables provided by users in the DBB YAML configuration files, some tasks look for inputs and generate outputs to the zBuilder Build Context. The Build Context is a dynamic storage area passed into each task being executed by the zBuilder and is used for task-to-task communication.