BMC Compuware Topaz for Total Test

Automate your build-test-deploy process through integrations with leading pipeline technologies such as Jenkins, Digital.ai Release, CloudBees Flow, and SonarSource SonarQube.

• Automate the creation of virtualized and non-virtualized tests, saving valuable time, and ensuring developers have a regression test suite that covers all foreseeable failure scenarios
• Execute only the test cases related to changed programs, speeding software delivery, and saving on mainframe resources
• Integrate BMC Compuware ISPW source code management so that when a developer promotes a change in ISPW, the pipeline will automatically execute the right tests based on those changes
• Collect and analyze code coverage metrics via BMC Compuware Xpediter to understand what part of the program code was covered by a specific test case
• Execute virtualized and non-virtualized test cases on different systems based upon available test environments—Topaz for Total Test automatically transfers the test cases as well as all virtualized programs, commands, and data needed

By simply clicking a Record button, the developer can submit a job that will execute the program to be tested and automatically record a test case and related virtualized test assets, including program stubs and test data from Db2, IMS, CICS, and datasets.

• Saves test assets so they can be used in later testing to virtualize real data
• Virtualizes (stubs out) program-to-data, program-to-subprogram calls, and IMS and CICS API calls, and returns data for only what is programmed into the test
• Verifies that programs consistently return the same data before and after code changes so developers can determine if any bugs were inadvertently introduced when code changes were made

• Supports non-virtualized testing of load modules on an LPAR in batch and CICS using real data and subsystems
• Programs can be written in COBOL, PL/I, or Assembler
• Define non-virtualized tests in a test scenario, and then record a test or manually specify input and expected output data for the linkage section of the module
• Use test scenario elements to create a sequence of steps (e.g. set up data in datasets and Db2) before testing programs
• Execute programs by providing input data and verifying output data, and finally verify data created by the program in Db2 and datasets
• Test scenarios can be used to test complex batch jobs and create an integration test of multiple program interaction