Set Topaz for Total Test Preferences

When starting Topaz for Total Test for the first time, review and set the Topaz for Total Test preferences, especially, you must Setup Database Access in the Functional Test  and establish your Repository connection in the Repository Server preferences to access all Non-virtualized Test features of Topaz for Total Test.

Preferences

Topaz for Total Test preferences allow you to control settings and defaults for the various functions in Topaz for Total Test. To view or change your preferences, click Window>Preferences. The Preferences dialog box appears. Expand Compuware and select Topaz for Total Test.

When you change your preferences settings, the updated preferences will be remembered the next time you start Topaz for Total Test. To restore the default settings, click Restore Defaults. Then click Apply or OK to accept your changes.

Preferences Settings

  • Logging format: Select the logging format from these choices:
    • Console logging
    • Eclipse logging
    • Topaz logging

The default is Topaz logging.

  • Logging level: Select the logging level from these choices:

    • ALL
    • TRACE
    • DEBUG
    • INFO
    • WARNING
    • ERROR.

    The default is INFO.

  • Report Generator: Select the only choice:

    • Default Topaz for Total Test Result Report Generator
  • Default JCL: In the JCL Jobcard field, specify the default job card information for Topaz for Total Test batch jobs on the mainframe when using the Unit Test runner.jcl. The variable ${TOTALTEST_JOBCARD} in the Virtualized Test (Unit Test) runner JCL templates will then load the default jobcard information you specify here. See also Create JCL Template.
  • Dataset high-level qualifier: (deprecated, optional, only used for classic Test Run dialog) Specify a high-level qualifier other than the default TSO User ID to be used when Topaz for Total Test allocates datasets on the mainframe during test execution. For the new Execution Context dialog, the dataset high-level qualifier is defined in the Environment/Connections definition in the Repository Server or the Total Test Configuration Project project. For more information, see Using-Non-virtualized-Test-without-the-Repository-Server.
    The default is your TSO User ID.
  • Maximum number of group redefines (default unlimited): (Optional) If your test program stubs include a high number of group redefines that affect the Stub Editor performance negatively, you may use this preference setting to limit the number of group redefines that Topaz for Total Test displays in the Stub and Results Editor.
    Valid values: 1-9999999. The default is no limit.
  • Use the classic Test Run dialog (deprecated) when running unit tests: (Optional) Starting with Release 20.04.01, Virtualized Test and Non-virtualized test use a common Execution Context dialog featuring dynamic JCL generation. Select this option to use the classic Test Run dialog. The classic Test Run dialog will be removed in a future release.
    By default, this selection is unchecked.
  • Enable stubbing proxy IMS DL/I calls to subprograms: (Optional) By default, this selection is unchecked, effectively turning off capturing of entry PCB data. During Test Generation using Xpediter, for programs that are marked as IMS, for every CALL Total Test encounters, it also collects current values on the USING statement. If the data on the USING statement is very big, that can result in collecting a lot of seemingly unnecessary data. Selecting this setting, will capture all of the entry PCB data and create stubs for each call to subprograms.
  • Maximum number of successful results to display in report: By default, the Report Editor displays up to 1000 successful results. Use this setting to lower or raise the limit. This setting only limits the display, not the actual results. Display of unsuccessful results remains unlimited.
    Valid values: 1-9999999999. The default is 1000.
  • Exclude successful string results containing nulls or spaces: Checking this setting will not display successful string result that are nulls or spaces. This setting only limits the display, not the actual results. Display of unsuccessful string results remains unlimited. By default, this selection is unchecked.
  • Generate result files: Select the desired result file formats to be generated during execution. If previous executions of your test generated any of the not selected result file formats, they will be deleted for the next execution. Select any or all of these formats:
    • JUnit
    • Sonar
    • HTML
    • XML

Additional Preferences Settings

When you expand the Topaz for Total Test entry in the Preferences dialog box, these additional preference pages appear:

Functional Test (Non-virtualized Test)

Review the available settings. Most likely you can accept the default settings. Pay attention to Folder with database jar files for Database Access.

Setup Database Access

If you are creating test scenarios that contain Db2 select statements, then you need to complete the following steps to configure Non-virtualized Test to use your Db2 driver and Db2 license.

  1. Get the Db2 jar files for your Db2 installation. Typically, there are two files, one with the Db2 driver and one with the Db2 license.
  2. Copy the Db2 jar files to the Non-virtualized Test directory under your user directory. Create the directory if it does not exist. The directory path can be found and changed under Windows > Preferences > Compuware > Topaz for Total Test > Functional Test > Folder with database jar files.

Repository Server

Important

From release 20.05.01 onwards, 

Topaz for Total Test

 uses the 

CES

 authentication to access the 

Topaz for Total Test

 Repository Server if you are also using 

CES

 Release 20.05.01 or later.

  1. Select the Use Repository Server check box in order to use Non-virtualized Test (Functional Test) with the Repository Server. This is the preferred choice.
    Uncheck Use Repository Server only if you want to use Non-virtualized Test without access to the Repository Server. That is required if no Repository Server has been created. For more information, see  Using Non-virtualized Test without the Repository Server.
  2. Click on the CES link in the statement beginning with "If you are using a Compuware Enterprise Services…" to validate your CES server connection.

a. In the CES Enterprise Services preferences dialog, enter or verify your CES server URL, for example:

http://<host>:<port>/

b. Click the Validate Connection button. The successful validation will return a message with the CES server release.

c. Click Apply.
If it is 20.05 or later, you are all set. When you return to the Topaz for Total Test Repository Server preferences, the Alternate repository server URL field and related check-box and button are greyed out.
If it is prior to 20.05, return to the Topaz for Total Test Repository Server preferences where you can now specify the Alternate repository server URL.

Alternate repository server URL for CES Releases prior to 20.05

  1. Setup the URL to the Topaz for Total Test Repository Server in order to use all of the Non-virtualized Test capabilities.

  2. Enter the URL for the Topaz for Total Test Repository Server at your network, that is the CES host and port followed by /totaltestapi/, for example:

    http://<host>:<port>/totaltestapi/
  3. Click Refresh token to get authorization from the server.
  4. Enter User ID and password to request authentication token from the server. Select Save password (default) so Topaz for Total Test will automatically refresh the authentication token. If Save password is not selected, you will have to reenter your credentials after the token expires.
  5. Click Apply or Apply and Close.

Special Considerations:

  1. If you don’t have installed the SSL certificate from the server in the JRE trust store, you will be asked to install the certificate.
  2. If you are working on a Mac or Linux, you might not have permissions to change the JRE certificate file. Then you might go to the next step to disable certificate checking.
  3. If the SSL certificate is invalid, you will see this error License server inaccessible. Then select the option Allow invalid SSL certificates…. This will disable certificate checking. Try again.
  4. For IBM based products like IDz that use an IBM Java and use a server with a certificate that is not TLSv1 an error dialog may appear. If this appears, the following steps need to be followed to use HTTPS to connect to the server.

    1. Change the eclipse.ini file and add the following below the line containing –vmargs. This will instruct IBM Java to allow other TLS versions.

      -Dcom.ibm.jsse2.overrideDefaultTLS=true
    2. Start/Restart the product.

Editor preference pages

Each of the Editor preference pages specify the default column width for each of the display columns in the Topaz for Total Test editors.

  • Test Interface Editor
  • Test Scenario Editor
  • Test Structure Editor
  • Test Stub Editor

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*