In this section:

About Coverage Data Storage

Coverage data can consume substantial storage. In order to preserve space, DTP keeps coverage data for the last two builds by default. Data for older builds in the filter will be removed during regular database pruning. If you choose a pruned build when configuring widget settings, the following message is displayed:

''No data available. Target build does not have details data."

See Configuring Data Retention Settings for instructions on customizing test and coverage storage settings.

The coverage data retention settings do not apply to the following widgets:

• Jenkins Cobertura Coverage - Percent
• Jenkins Cobertura - Summary

Support for Application Coverage

If you are collecting Application Coverage, there may be times when only the runtime coverage data is sent to DTP (without corresponding static coverage data). In these instances, various coverage widgets will attempt to show as much information as possible. There are two use cases:

1. Runtime coverage data without any static coverage data.
   • In this case, you will see N/A for % Coverage and N/A for Total Lines. This widget only displays the Line Covered.
2. Runtime coverage data with some static coverage data (some runtime coverage data do not have corresponding static coverage data).
   • In this case, you will see an asterisk next to the % Coverage. This means that runtime coverage data, without corresponding static coverage data, is not included in the widget. You can drill into the Coverage Explorer for more details.

For more information about Application Coverage, see:

• Jtest application coverage
• dotTEST application coverage
• SOAtest and CTP application coverage

Coverage - Percent

This widget shows the percentage of line coverage for a build. The widget can show coverage for either the most recent build or a baselined (locked) build. See Locking and Unlocking a Build (Baseline) for additional information.

Widget Configuration

Actions

Click on the widget to open the Coverage Explorer filtered by build and filter. See Coverage Explorer for additional information.

Custom Dashboard Properties

You can add this widget to your custom dashboards by specifying the following properties in the dashboard definition JSON file (see Custom Dashboard Templates for details): 

"name": "coverage",
"type": "native",
"uuid": "a12eefab-25b6-4127-9ad6-a472208142b4"

Coverage - Summary Trend

This widget shows the following information for the selected filter:

• Current level of line coverage percentage of coverage.
• Change in line coverage from the previous day (taken from the Period setting).
• Change in line coverage as a line chart from the baseline build to the target build.

Widget Configuration

Actions

• Click on the widget to open the Coverage Explorer (see Coverage Explorer).
• Hover over points in the trend line to show coverage for the reported build.

Custom Dashboard Properties

You can add this widget to your custom dashboards by specifying the following properties in the dashboard definition JSON file (see Custom Dashboard Templates for details): 

"name": "coverage",
"type": "native",
"uuid": "bfd6867c-81b8-40f1-ba01-6b3af8914ac1"

Coverage - Trend

This widget shows the change in line coverage over the specified period of time. Gaps in the trend line represent builds that do not have coverage information. 

Widget Configuration

Actions

You can perform the following actions:

1. Click on the widget to open the Coverage Explorer. See Coverage Explorer.
2. Hover over an area in the graph to view the coverage for that build.

Custom Dashboard Properties

You can add this widget to your custom dashboards by specifying the following properties in the dashboard definition JSON file (see Custom Dashboard Templates for details): 

"name": "coverage",
"type": "native",
"uuid": "31e7cb3c-1319-4d33-8157-8118771ee3f1"

Jenkins Cobertura Coverage - Percent

This widget shows the percentage of code covered, number of lines of code covered, and total number of lines for the specified job as reported by the Cobertura plug-in for Jenkins. The Jenkins API must return English for the widget to function properly.

Widget Configuration

Actions

Click the widget to view the code coverage information in Jenkins in a new window.

Custom Dashboard Properties

You can add this widget to your custom dashboards by specifying the following properties in the dashboard definition JSON file (see Custom Dashboard Templates for details): 

"name": "test.jenkins_cobertura_coverage"
"type": "native",
"uuid": "b9a1c83e-652b-458c-8eb3-e0159f6083be"

Jenkins Cobertura - Summary

This widget shows the code coverage information for the specified job reported by the Cobertura plug-in for Jenkins. It includes the number of lines of code, total lines of code, and build ID of the last run. The Jenkins API must return English for the widget to function properly.

Widget Configuration

Actions

Click the widget to view the code coverage information in Jenkins in a new window.

Custom Dashboard Properties

You can add this widget to your custom dashboards by specifying the following properties in the dashboard definition JSON file (see Custom Dashboard Templates for details): 

"name": "Jenkins Cobertura - Summary",
"type": "native",
"uuid": "86ee93c1-58d3-4ca7-89d7-cda9b095478c"

Modified Coverage - Percent

This widget helps reduce the testing scope associated with code changes (such as implementing a feature) so testers can focus on the uncovered code and increase their testing efficiency. It also helps teams maintain an audit trail of the risk associated with untested changes. Modified Code Coverage performs the following actions:

1. Analyzes the coverage data associated with file modifications.
2. Determines the lines of code in those files that were changed. 
3. Reports which of the not-yet covered new/modified lines of code can be covered.

The artifact is implemented as a widget that reports the coverage percentage for the lines of code that have been changed since a baseline build. It also graphically indicates the coverage achieved on each new or modified line of code.

Requirements

• At least one filter in DTP must be configured to receive Run Configurations from coverage analysis runs.
• Test and coverage data from the following Parasoft tools are supported:
  • C/C++test Standard, dotTEST, and Jtest 10.4.3 or later.
  • C/C++test Professional 10.4.3 or later.
  • SOAtest 9.10.7 or later.
• Reports published to DTP must have consistent information. Instead of presenting code coverage data, the drill-down report may show N/A if one or more of the reports for the builds lacks proper resource information. Verify that the source-related settings for code analysis tool sending reports to DTP have been properly configured. Refer to the tool’s documentation for additional information.

• DTP must have access to the source code. You can integrate DTP with your source control system or configure the code analysis tool to publish sources to DTP as part of their analysis. For details, see Configuring Source Code Views. 

  Information about sources must be consistent

  If DTP reads sources from Parasoft code analysis and testing tool reports, make sure that source information is always included by setting the report.dtp.publish.src property to min or full in either the tool's .properties configuration file (see the tool's documentation) or in the shared project settings in DTP (see Configuring Parasoft Tool Settings for Projects). If DTP reads sources from source control, ensure that the scontrol and report.scontrol properties are properly configured. Gaps, incomplete, or inconsistent source information will prevent the Modified Coverage extension from properly displaying the data.

Locking Builds

DTP continually receives and cleans large amounts data from its database. By default, the unit test and coverage information associated with a build will be automatically deleted after two more builds containing unit test and coverage information are reported to the same DTP project. You can lock builds that contain your baseline data to prevent it from being removed. We recommend keeping the baseline build ID locked while using the build for Modified Coverage and/or for DTP audit reports. You should make sure to lock baseline builds that contain coverage and test data. See Locking and Archiving Builds for details.  

Widget Configuration

By default, Baseline Build is set to Previous Build and Target Build is set to Latest Build with Data. The widget will automatically select the two most recent builds, but these builds may not contain test and coverage details. You should check the Build Administration page in DTP (see Build Administration) and use an appropriate baseline and target build when configuring the widget.

The widget shows the percentage of modified lines of code that have been covered with tests from the baseline build to the target build.

Actions

Click on the widget to open a detailed drill-down report that shows the coverage for each file:

Red and green are used to highlight testable code that was changed between the baseline build and the target build. Green indicates that at least one test case covered the code. Red indicates that no test cases covered the code.

Custom Dashboard Properties

You can add this widget to your custom dashboards by specifying the following properties in the dashboard definition JSON file (see Custom Dashboard Templates for details): 

"name": "modified_code_coverage",
"type": "native",
"uuid": "eeba8492-f110-4046-af7e-063cbcdf033f"

Portfolio - Coverage Statistics

This widget shows the coverage statistics for the filters in the specified portfolio. Refer to the Configuring Portfolios section for details about configuring portfolios in DTP.

The widget shows the coverage percentage, lines covered, and total lines.

If you are a member of a project associated with a filter in the portfolio, you will see an entry in the widget for that filter. See Adding Teams to Projects for additional information about team membership or Permissions for information about built-in user permissions in DTP.

Widget Configuration

Actions

Click on a link to open the Coverage Explorer view for that result. 

Click on a column header to sort the data.

Custom Dashboard Properties

You can add this widget to your custom dashboards by specifying the following properties in the dashboard definition JSON file (see Custom Dashboard Templates for details):

"name": "portfolio.coverage_statistics",
"type": "native",
"id": "4cf20b98-c246-4f5e-8813-72cbaa3f1f50"

Resource Groups - Top 10 Tree Map

This widget shows the ten resource groups in the filter with the highest percentage of coverage. Each resource group in represented in the widget as a tile. Larger tiles with a deeper color represent resource groups with higher percentages of coverage. 

 A resource group is a collection of resources (files and/or folders) defined by a set of one or more Ant file patterns. See Adding Resource Groups to Projects for additional information about resource groups.

Widget Configuration

Actions

Mouse over a tile to view the name of the resource group and coverage. Click on a tile view coverage information about the resource group in the Coverage Explorer.

Custom Dashboard Properties

You can add this widget to your custom dashboards by specifying the following properties in the dashboard definition JSON file (see Custom Dashboard Templates for details): 

"name": "Resource_Groups"
"type": "native",
"id": "2e096c46-3f23-4997-a1a2-664d582522e8"

Resource Groups - Top 5 Table

This widget shows the five resource groups with the highest percentage of coverage. The widget renders a table that you can sort in ascending or descending order in the settings.

Widget Configuration

Actions

Click on a resource group name to view coverage information about the resource group in the Coverage Explorer. 

Click on the more... link to view the Resource Groups Report.

Custom Dashboard Properties

You can add this widget to your custom dashboards by specifying the following properties in the dashboard definition JSON file (see Custom Dashboard Templates for details): 

"name": "Resource_Groups"
"type": "native",
"id": "48b9f13c-a968-484d-a69a-48a2cdf39c3f"