Getting Started
This Guide is intended to walk you through installing/updating, configuring, deploying, and troubleshooting Code Coverage.
Code Coverage is an advanced application analysis tool that provides the ability to create reports detailing testing efficiency and risk metrics for mainframe COBOL, PL/I, and High-Level Assembler programs.
Code Coverage works in conjunction with BMC's mainframe test and debugging tools Code Debug CICS and Code Debug TSO.
Product architecture
Code Coverage is made up of a number of components accessible from either a standard terminal or from Workbench for Eclipse, an eclipse-based modernized user interface.
The steps in a Code Coverage debugging session workflow are:
Number | Description |
|---|---|
1 | A Workbench for Eclipse or mainframe Code Debug CICS or Code Debug TSO user initiates a debugging request for their user application with Code Coverage turned on. |
2 | Code Debug intercepts the user application for debugging. Supported Workbench for Eclipse environments include batch, TSO, Db2, and IMS. Supported Mainframe environments include batch, CICS, TSO/ISPF, Db2, IMS, and BTS. |
3 | BMC AMI Common Shared Services (CSS)—a component of BMC AMI Enterprise Common Components (ECC)—locates the source listing. It can be either stored in the CSS source shared directory (or DDIO) or embedded in the load module via Embedded Source Support. |
4 | The interactive debugging session begins. Code Coverage statistics are gathered. The source listing is displayed to give the user a familiar context for debugging. |
5 | When the session is completed, Code Coverage data is written to the Code Coverage repository. |
For instructions about Workbench for Eclipseintegration, go to Milestone 9.
You can get to know the terms used with the glossary below: