Renaming of stub using sub-program name

When you record a Unit Test, the Sub-program Rename feature creates individual stubs for each combination of sub-program name and sub-program rename value. This method facilitates convenient access to stubs created during the testing phase based on the sub-program names.

Stub Labeling Convention

Stubs are labeled in the format xxxxxxxx_yyyyyyyy_zzzzzzzz_##.stub, where:

• xxxxxxxx:  Main program name
• yyyyyyyy: Target program name
• zzzzzzzz: Sub-program rename value
• ##: Version number

Example:
Consider CWXTCOBB_ZCALLPGM_CWXTDATE_01.stub, where CWXTCOBB is the main program name, ZCALLPGM is the target program name, CWXTDATE is the sub-program rename value, and 01 is the version number.

Description Value

When viewing or modifying stubs, the sub-program rename value will serve as the Description value. 

Impact on Scenario Result Report

After a Unit Test execution, the sub-program rename value becomes the Target or Stub value on the Problems tab in case of assertions. This immediate association simplifies debugging by linking reported problems to specific sub-program instances.

Executed Call Value on the Report Tab

In the Report tab, the sub-program rename value acts as the executed call value for separate stubs. This correlation ensures a clear overview of the executed calls during Unit Testing, which aids in interpreting the results. To summarize, displaying sub-program names in stub information and using sub-program rename values improves the accessibility of the stubs.