Creating and Preparing a Test Project

Follow the steps and procedures to create and prepare a test project. Total Test users need to execute these steps for proper test setup.

Create New Total Test Project

To start with a brand-new Total Test project:

Click on the Create a new Total Test project toolbar icon or select from the menu File > New > Project > BMC > Total Test Project.
Alternatively, just click on the New Project symbol available in the toolbar and select BMC > Total Test.
The New Total Test Project wizard will appear.
- Enter a project name in the Name field.
- Enter a folder name in the Folder field.
  Multiple folder levels can be entered in the folder name. Example "MyTests/SimpleDB2".
- Click Finish. The new Total Test project appears in Project Explorer.

If you already have a Total Test project that you want to import into your workspace:

Simply use the standard project import mechanism.
From the menu, select File > Import, then in the list select General > Existing Projects into Workspace.
Once imported, Total Test will recognize the project as a Total Test project.

Create JCL Template

To run tests,Total Test Virtualized Test requires at least one JCL template in the JCL folder of the project to be used for execution on the target platform when using the Use JCL defined in the project option in the Execution Context dialog or when using the classic Run Test dialog. Refer to Execute Test Scenarios.

The sample JCL templates (Runner.jcl, RunnerBmp.jcl, RunnerBMPDB2, and RunnerDB2.jcl) are only created if the Total Test preference Use the classic Test Run dialog is checked. Use Runner.jcl for tests that do not use live Db2 or live IMS BMP.

Important

If your test case includes live DB2, use JCL based on the RunnerDB2.jcl template.
If your test case includes live IMS BMP, use JCL based on the RunnerBmp.jcl template.
If your test case includes both live DB2 and live IMS BMP, use JCL based on the RunnerBmpDB2.jcl template.

JCL Customization is Required

Follow the instructions inside the sample JCL as they require some customization to meet the requirements of your specific test environment.

Make sure your STEPLIB DD points at your site's Enterprise Common Components (ECC) Release 17.02 or newer load library (CPWR.MLCXnnn.SLCXLOAD), for example hlq.CPWR.MLCX170.SLCXLOAD. For more information, see Enterprise Common Components Installation and Configuration Guide for Release 17.02.

Important

Make sure a job or step REGION= parameter specifies an appropriate value.
REGION=0M allows Test Runner to obtain all the storage it needs. When specifying any other value for REGION=, be aware that Test Runner requires 40 MB more, in most cases, than the unit test target program would require on its own.
For example, if a target program requires REGION=200M to run on its own, then REGION=240M should be specified.
${TOTALTEST_JOBCARD} will load the Total Test default jobcard specified in Window > Preferences > BMC > BMC AMI DevX Total Test. See also Set-Total-Test-Preferences.
When the COBOL program with Db2 is compiled with NODYNAM, the Db2 library is not required in Runner.jcl.
When the COBOL program with Db2 is compiled with DYNAM, the Db2 library is required — or, at least, DSNHADDR and DSNHADD2 must be available to the job, whether via LINKLIST or any other library on STEPLIB, Runner.jcl.
When Db2, CICS, IMS, or statically-linked subprogram stubs are in use, the Test Runner needs access to the program's source listing at runtime. We strongly recommend the use of Embedded Source Support (ESS), but if not in use the Test Runner will automatically search for the DDIO in both the load module's IDR as well as in the DDIO used during the Code debug session. If for any reason those two options do not work, SLSFnnn DDs may be used to manually specify the location of the DDIO, where nnn goes from 001 to 008.
If Code Coverage fails and indicates "No data matched the specified criteria", the following DD may have to be added to your Runner.jcl:

XPSL0004 DISP=SHR,DSN=DSN.OF.DDIO.WITH.PROG.LISTING

Adjust Project Properties

To do this:

Right-click on your project's name in the Project Explorer to the left, then, from the context menu, select Properties.
From the list shown, select Total Test. Usually, you do not need to make any modifications in the general Total Test entry.
Please refer to Project-Properties for a description of the options there.

If you expand the Total Test entry on the left, you will see one more entry: COBOL Copybook Importer.

COBOL Copybook Importer

You do not need to make any modifications in the COBOL Copybook Importer section unless your copybooks contain special characters that need to be replaced or removed. If so, click Add to add one or more string replacements. In order to remove strings, just leave the replacement entry empty.

You are now ready to go.