Results view interface overview
Code coverage results are organized in the results view. This view opens automatically after a run or you can open it manually from the Open View menu or the Code Coverage icon on the toolbar. Results are grouped by the type of code coverage result or the location where results are stored. Information is displayed for Name, Status, Coverage, Level, Analyzed Date, and Additional information. Double click or right-click a result to open a report, compare results, merge results, and more. When you open a report for further analysis, for most report types the information is displayed in the editor area above the results view.
The following result groups are available:
- Workspace Results
- Results captured by the client for compiled languages such as COBOL and PL/I.
- Java™ Workspace Results (Deprecated)
- Java and JUnit results that were collected from previous releases and migrated into *.cczip result format.
- Local result locations
- By default, results are stored in the workspace. But if you have configured a local result
location outside of your workspace, the results stored there will be displayed in the section with
the icon
. - Remote result locations
- By default, results are stored in the workspace. But if you have configured a remote result
location on another system, the results stored there will be displayed in the section with the icon
. - CCS result locations
- Results stored using Code Coverage Service (CCS) can be stored on the local client
or on a remote system. The interaction with the results is completely through a RESTful API and
requires only the URL of the CCS server, for example,
http://localhost:8006.
Notes:
- Workspace Results is a built-in result location and appears in the view by default. You can see Java Workspace Results (Deprecated) only if you have Java code coverage results in a previous release of this product.
- Local, remote, and CCS result locations appear only after you manually add them. For more information about how to add a result location, see Working with result locations.
- You can start a CCS server with the headless code coverage collector or Remote Debug Service. For more information, see Starting and stopping the headless code coverage daemon and Customizing with the sample job EQARMTSU.
