Unit Test Options tab for CICS

Stubs

For CICS, live program execution is not available for unit test execution. Therefore, stubs will always be created for sub-program, Db2 and CICS calls.

Important

For Program stubs to be created, the sub-program(s) must be called while Code Debug is gathering the data to send to Total Test. In order for Code Debug to get call data, the call parameters and results data must actually execute the sub-program during the captured debug session.

Create assert condition for data passed into sub-programs

Check (default) the Create assert condition for data passed into sub-programs checkbox for Total Test to generate sub-program assertions for sub-program stubs. Sub-program assertions validate all of the data that is being passed into a sub-program call just like a Write Assertion validates all the data that is passed into a Write I/O call. Useful if I/O is done inside of sub-program and can't be validated by write assertions.
Uncheck if assert conditions should NOT be created.

Processing Options

The dialog contains the following fields under the Processing Options heading.

Overwrite existing stubs

Check the Overwrite existing stubs checkbox if you want to replace the contents of previously created, same named, stubs with the data to be collected from this unit test data collection.
If left unchecked, Total Test will create a copy of the same named stubs, and identify each new set of Data Stubs with a 2 digit set identifier.

Example

Existing stub: CWXTCOB_EMPFILE_READ.stub
New stub: CWXTCOB_EMPFILE_01_READ.stub

Important

If you have already assigned a stub in a Test Scenario, remember to update the Test Scenario if you want to use more recently created stubs (see also Stubs Input Data).

OK

After filling out all fields and setting the desired settings in the dialog box, click OK to create the test case.

Cancel

Click Cancel to close the dialog box without initiating creation of the test case.