×
Find plugins

Compuware Topaz for Total Test2.0.1Minimum Jenkins requirement: 2.21ID: compuware-topaz-for-total-test

Plugin Information

Plugin ID

compuware-topaz-for-total-test

Changes

In Latest Release
Since Latest Release

Latest Release
Latest Release Date
Required Core
Dependencies

2.0 (archives)
Nov 06, 2017
2.21
compuware-common-configuration (version:1.0.2)
cloudbees-folder (version:5.12)
credentials (version:2.0.4)

Source Code
Issue Tracking
Pull Requests
Maintainer(s)

GitHub
Open Issues
Pull Requests
Paul Allard (id: cpwr_jenkins)

Usage

Installations

2017-Aug 14
2017-Sep 24
2017-Oct 32

The Compuware Topaz for Total Test plugin allows Jenkins users to run test suites and test scenarios for unit testing mainframe programs.

Overview

Compuware's Topaz for Total Test is a testing product with automation to speed testing development and provide higher confidence during program deployment process.The plugin allow Jenkins users to run test scenarios and test suites.

Prerequisites

The following are required to use this plugin:

  • Jenkins
  • Jenkins Credentials Plugin
  • Topaz Workbench CLI. Refer to the Topaz Workbench Install Guide for instructions.
  • Topaz for Total Test license.
  • Host Communications Interface

 

Installing in a Jenkins Instance

 

  1. Install the Compuware Topaz for Total Test plugin according to the Jenkins instructions for installing plugins.  Dependent plugins will automatically be installed.
  2. Install the Topaz Workbench CLI on the Jenkins instances that will execute the plugin.  The Topaz Workbench CLI is available on the Topaz Workbench installation package.  If you do not have the installation package, please visit go.compuware.com.  For Topaz Workbench CLI installation instructions, please refer to the Topaz Workbench Install Guide.

 

Configuring Host Connections

  1. In the Jenkins system Jenkins/Manage Jenkins/Configure System screen, go to the Compuware Configurations section, do one of the following:

    • In the Windows Topaz Workbench CLI home field, point to the Windows installation location of the CLI. If necessary, change the default values given to match the correct installation location.

    • In the Linux Topaz Workbench CLI home field, point to the Linux installation location of the CLI. If necessary, change the default values given to match the correct installation location.

    Note: The Topaz Workbench CLI must be installed on the machine that is configured to run the job.

  2. If no host connection appears in the Host Connections section, click Add Host Connection and add a host connection by entering the following information:

    • In the Description field, enter a description of the connection.

    • In the Host:port field, enter the z/OS host to connect to.

    • From the Code page list, select the desired code page to be used for this connection. The code page is used to translate data sent to and from the host. The default is 1047.

    • In the Read/write timeout (minutes) field, enter the number of minutes for the plugin to wait for a response from the host before timing out.

    Note: Click Delete Host Connection to delete an existing connection.

Executing tests

  1. Install the Compuware Topaz for Total Test plugin according to the Jenkins instructions for installing plugins.  

  2. In the Jenkins system configuration page's Topaz Workbench CLI box, point to the Windows and/or Linux installation location(s) of the CLI. If necessary, change the default values given to match the correct installation location(s).

    Note: The Topaz Workbench CLI must be installed on the machine that is configured to run the job.

  3. On the project Configuration page, in the Build section click Add build step button and select Topaz for Total Test.

  4. In the Host:port field, enter the z/OS host to connect to.

  5. In the Login credentials list, select the stored credentials to use for logging onto the host. Alternatively, click Add to add credentials using the Credentials Plugin. Refer to the Jenkins documentation for the Credentials Plugin.

  6. In the Test Project Folder field, enter the path to the folder containing the Topaz for Total Test project.

  7. In the Test scenario/suite field, enter the name of the test scenario or test suite to be executed.

    Note: Wildcards can be used to select multiple test scenarios or test suites.
    Note: ALL_SCENARIOS or ALL_SUITES can be used to select all test

  8. In the JCL field, enter the name of the JCL file to use.

  9. Optionally click the Code Coverage button to have Code Coverage information generate during the test run.
    1. In the Code Coverage Repository field, enter the dataset name of the Code Coverage repository to be used.
    2. In the System name field, enter the system name, If left blank defaults to the test scenario or test suite name.
    3. In the Test Id field, enter a name for test test. If left blank defaults to the test scenario or test suite name.
  10. Optionally click the Execute Options button to change execution options.
    1. Check the Use Stubs checkbox if the test is to be run using stubs. if Stubs are not going to be used uncheck the checkbox. The default is to use Stubs.
    2. Check the Delete temporary files checkbox if temporary files are to be deleted after the test runs. Uncheck the checkbox if temporary files are to be saved. The default is to delete temporary files.
    3. In the High Level Qualifier field, enter the high level qualifier to be used to allocate z/OS datasets. If specified not defaults to the user id specified in the Login Credentials
  11. Click Save.

Product Assistance

Compuware provides assistance for customers with its documentation, the FrontLine support web site, and telephone customer support.

FrontLine Support Web Site

You can access online information for Compuware products via our FrontLine support site at http://go.compuware.com. FrontLine provides access to critical information about your Compuware products. You can review frequently asked questions, read or download documentation, access product fixes, or e-mail your questions or comments. The first time you access FrontLine, you must register and obtain a password. Registration is free.

Compuware also offers User Communities, online forums to collaborate, network, and exchange best practices with other Compuware solution users worldwide. Go to http://groups.compuware.com/ to join.

Contacting Customer Support

At Compuware, we strive to make our products and documentation the best in the industry. Feedback from our customers helps us maintain our quality standards. If you need support services, please obtain the following information before calling Compuware's 24-hour telephone support:

  • The name, release number, and build number of your product. This information is displayed in the About dialog box.
  • Installation information including installed options, whether the product uses local or network databases, whether it is installed in the default directories, whether it is a standalone or network installation, and whether it is a client or server installation.
  • Environment information, such as the operating system and release on which the product is installed, memory, hardware and network specification, and the names and releases of other applications that were running when the problem occurred.
  • The location of the problem within the running application and the user actions taken before the problem occurred.
  • The exact application, licensing, or operating system error messages, if any.

You can contact Compuware in one of the following ways:

Phone

  • USA and Canada: 1-800-538-7822 or 1-313-227-5444.
  • All other countries: Contact your local Compuware office. Contact information is available at http://go.compuware.com.

Web

You can report issues via FrontLine.

Note: Please report all high-priority issues by phone.

 

Corporate Web Site

 

To access Compuware's site on the Web, go to http://www.compuware.com. The Compuware site provides a variety of product and support information.

Mail

Customer Support
Compuware Corporation
One Campus Martius
Detroit, MI 48226-5099

Change Log

Version 2.0.1

  • Fix display and processing of CodeCoverage information.

Version 2.0.0

  • The plugin now integrates with the Compuware Common Configuration plugin which allows the Host Connection configurations and Topaz Workbench CLI to be defined centrally for other Compuware Jenkins plugins instead of needing to be specified in each Jenkins project's configuration.  Host Connection configuration is now defined in the Jenkins/Manage Jenkins/Configure System screen. 

Version 1.8.2

  • Added dsiplay of Jenkins and Compuware Topaz for Total versions in Jenkins Console log.
  • Fix Linux global configuration

 

Version 1.8

  • Initial release.




 

ArchivesGet past versions
Labels
This plugin has no labels