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 only apply to the following widgets:
Coverage data for the following widgets is stored differently and are not affected by data retention settings in DTP:
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
| Title | Enter a new title to replace the default title that appears on the dashboard. |
|---|---|
| Filter | Choose Dashboard Settings to use the dashboard filter or choose a filter from the drop-down menu. |
| Coverage Image | Choose a coverage image from the drop-down menu to show coverage data in the widget. See Associating Coverage Images with Filters. |
| Target Build | Choose a build from the drop-down menu to serve as the current data for comparison. |
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
| Title | Enter a new title to replace the default title that appears on the dashboard. |
|---|---|
| Filter | Choose Dashboard Settings to use the dashboard filter or choose a filter from the drop-down menu. |
| Period | Choose Dashboard Settings to use the dashboard date range or choose a period from the drop-down menu. |
| Coverage Image | Choose a coverage image from the drop-down menu to show coverage data in the widget. See Associating Coverage Images with Filters. |
| Baseline Build | Choose a build from the drop-down menu to set the initial data for comparison. |
| Target Build | Choose a build from the drop-down menu to serve as the current data for comparison. |
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
| Title | Enter a new title to replace the default title that appears on the dashboard. |
|---|---|
| Filter | Choose Dashboard Settings to use the dashboard filter or choose a filter from the drop-down menu. |
| Period | Choose Dashboard Settings to use the dashboard date range or choose a period from the drop-down menu. |
| Coverage Image | Choose a coverage image from the drop-down menu to show coverage data in the widget. See Associating Coverage Images with Filters. |
Actions
You can perform the following actions:
- Click on the widget to open the Coverage Explorer. See Coverage Explorer.
- 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 requires a DTP Enterprise license.
Contact your Parasoft representative for additional information.
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
| Title | Enter a new title to replace the default title that appears on the dashboard. |
|---|---|
| Jenkins Server | URL of the Jenkins server, including the protocol (HTTP, HTTPS) and port. This field is required. |
| Jenkins Job | Name of the job. This field is required. |
| Jenkins User | Specify the user name of a user with access to the Jenkins application if you are not using anonymous access. |
| Jenkins Auth | Specify the password for a user with access to the Jenkins application if you are not using anonymous access. |
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
| Title | Enter a new title to replace the default title that appears on the dashboard. |
|---|---|
| Jenkins Server | URL of the Jenkins server, including the protocol (HTTP, HTTPS) and port. This field is required. |
| Jenkins Job | Name of the job. This field is required. |
| Jenkins User | Specify the user name of a user with access to the Jenkins application if you are not using anonymous access. |
| Jenkins Auth | Specify the password for a user with access to the Jenkins application if you are not using anonymous access. |
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:
- Analyzes the coverage data associated with file modifications.
- Determines the lines of code in those files that were changed.
- 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.
Upgrading users
If you are upgrading from a version of DTP prior to 2022.1 and were using the Modified Coverage widget from the Process Intelligence Pack, you will need to manually delete the old widget from your installation. To do so, delete the following file: <DTP_DATA_DIR>/grs/plugins/widgets/coverage.modifiedCodeCoverage.def.json.
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.srcproperty tominorfullin either the tool's .properties configuration file (see the tool's documentation) or in the shared project settings in DTP (see Configuring Parasoft Test Settings for Projects). If DTP reads sources from source control, ensure that thescontrolandreport.scontrolproperties 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.
This widget requires a DTP Enterprise license.
Contact your Parasoft representative for additional information.
Widget Configuration
| Title | Enter a new title to replace the default title that appears on the dashboard. |
|---|---|
| Filter | Choose Dashboard Settings to use the dashboard filter or choose a filter from the drop-down menu. |
| Period | Choose Dashboard Settings to use the dashboard period or choose a time range from the drop-down menu. |
| Baseline Build | Choose a build for comparison. By default, Previous Build is selected. |
| Target Build | Choose the build you want to compare the baseline build to. By default, Latest Build with Data is selected. |
By default, Baseline Build is set to Previous Build and Target Build is set to Latest Build. 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"
Resource Groups - Top 10 Tree Map
This widget shows the 10 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 (i.e., 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
| Title | Enter a new title to replace the default title that appears on the dashboard. |
|---|---|
| Filter | Choose Dashboard Settings to use the dashboard filter or choose a filter from the drop-down menu. |
| Period | Choose Dashboard Settings to use the dashboard date range or choose a period from the drop-down menu. |
| Coverage Image | Choose a coverage image from the drop-down menu to show coverage data in the widget. See Associating Coverage Images with Filters. |
| Target Build | Choose a build from the drop-down menu that contains the data you want to see. |
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
| Title | Enter a new title to replace the default title that appears on the dashboard. |
|---|---|
| Filter | Choose Dashboard Settings to use the dashboard filter or choose a filter from the drop-down menu. |
| Period | Choose Dashboard Settings to use the dashboard date range or choose a period from the drop-down menu. |
| Target Build | Choose a build from the drop-down menu that contains the data you want to see. |
| Sort By | Choose an order in which to present the data from the drop-down menu. |
| Coverage Image | Choose a coverage image from the drop-down menu to show coverage data in the widget. See Associating Coverage Images with Filters. |
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"
C/C++test Coverage Overview - Percent
This widget shows the percentage of test coverage for a run configuration within the filter and target build. Filters may contain several run configurations, which are designated by a session tag and the test configuration name. See Run Configuration for additional information.
This widget only shows coverage information for C/C++test Professional. C/C++test Standard, dotTEST, and Jtest report line coverage only, whereas C/C++test Professional is capable of reporting several coverage types, in addition to line coverage.
When configuring the widget, you can choose the following coverage types:
- Block Coverage
- Call Coverage
- Decision Coverage
- Function Coverage
- Line Coverage
- Modified Condition/Decision Coverage (MC/DC)
- Path Coverage
- Simple Condition Coverage
- Statement Coverage
Refer to the C/C++test Professional documentation for additional information about coverage types and how to collect coverage.
Widget Configuration
| Title | Enter a new title to replace the default title that appears on the dashboard. |
|---|---|
| Filter | Choose Dashboard Settings to use the dashboard filter or choose a filter from the drop-down menu. |
| Coverage Type | Choose a coverage type from the drop-down menu. to show coverage data in the widget. Refer to the C/C++test Professional documentation for additional information about coverage types. |
| Run Configuration | Choose a run configuration from the selected filter for which the coverage data will be presented. Run configurations are designated by session tag and test configuration name. See Run Configuration for additional information. |
| Target Build | Choose a build containing coverage data from the drop-down menu. |
Actions
Click on the widget to open the C/C++test coverage report. Refer to the C/C++test Professional documentation for additional information about reports.
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_overview" "type": "native", "id": "7e6bda96-1776-4b8f-b966-50971c1b7160"
C/C++test Coverage Overview - Trend
This widget shows the change in test coverage over time for a run configuration within the filter and target build. Gaps in the trend line represent builds that do not have coverage information for the specified coverage type. Filters may contain several run configurations, which are designated by a session tag and the test configuration name. See Run Configuration for additional information.
This widget only shows coverage information for C/C++test Professional. C/C++test Standard, dotTEST, and Jtest report line coverage only, whereas C/C++test Professional is capable of reporting several coverage types, in addition to line coverage.
When configuring the widget, you can choose the following coverage types:
- Block Coverage
- Call Coverage
- Decision Coverage
- Function Coverage
- Line Coverage
- Modified Condition/Decision Coverage (MC/DC)
- Path Coverage
- Simple Condition Coverage
- Statement Coverage
Refer to the C/C++test Professional documentation for additional information about coverage types and how to collect coverage.
Widget Configuration
| Title | Enter a new title to replace the default title that appears on the dashboard. |
|---|---|
| Coverage Type | Choose a coverage type from the drop-down menu. to show coverage data in the widget. Refer to the C/C++test Professional documentation for additional information about coverage types. |
| Filter | Choose Dashboard Settings to use the dashboard filter or choose a filter from the drop-down menu. |
| Period | Choose Dashboard Settings to use the dashboard date range or choose a period from the drop-down menu. |
| Run Configuration | Choose a run configuration from the selected filter for which the coverage data will be presented. Run configurations are designated by session tag and test configuration name. See Run Configuration for additional information. |
Actions
They x-axis represents the builds in the specified period. You can hover your pointer over an area of the widget aligned to a build to view the build ID name and precise coverage for the build.
Click on a the widget to open a dialog containing more detailed coverage information about the builds represented in the widget.
Click on a link in the Build column of the Coverage Trend dialog to open the C/C++test coverage report. Refer to the C/C++test Professional documentation for additional information about reports.
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_overview" "type": "native", "id": "93248a16-f3e0-4719-8cec-0706a13a1d20"
