In this section:
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:
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.
| 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 menu. |
| Coverage Image | Choose a coverage image from the menu to show coverage data in the widget. See Associating Coverage Images with Filters. |
| Target Build | Choose a build from the menu to serve as the current data for comparison. |
Click on the widget to open the Coverage Explorer filtered by build and filter. See Coverage Explorer for additional information.
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" |
This widget shows the following information for the selected filter:
| 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 menu. |
| Period | Choose Dashboard Settings to use the dashboard date range or choose a period from the menu. |
| Coverage Image | Choose a coverage image from the menu to show coverage data in the widget. See Associating Coverage Images with Filters. |
| Baseline Build | Choose a build from the menu to set the initial data for comparison. |
| Target Build | Choose a build from the menu to serve as the current data for comparison. |
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" |
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.
| 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 menu. |
| Period | Choose Dashboard Settings to use the dashboard date range or choose a period from the 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. |
You can perform the following actions:
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" |
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.
| Title | Enter a new title to replace the default title that appears on the dashboard. |
|---|---|
| Jenkins Server | Enter the URL of the Jenkins server, including the protocol (HTTP, HTTPS) and port. This field is required. |
| Jenkins Job | Enter the name of the job. This field is required. |
| Jenkins User | (Optional) Specify a username to access the Jenkins server. The user must have access to the project. If you do not provide a specific user login, the Jenkins server must allow anonymous read access for the Jenkins-based widgets to function properly. |
| Jenkins Auth | (Optional) Specify a password for the user to access the Jenkins server. The user must have access to the project. If you do not provide a specific user login, the Jenkins server must allow anonymous read access for the Jenkins-based widgets to function properly. |
Click the widget to view the code coverage information in Jenkins in a new window.
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" |
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.
| Title | Enter a new title to replace the default title that appears on the dashboard. |
|---|---|
| Jenkins Server | Enter the URL of the Jenkins server, including the protocol (HTTP, HTTPS) and port. This field is required. |
| Jenkins Job | Enter the name of the job. This field is required. |
| Jenkins User | (Optional) Specify a username to access the Jenkins server. The user must have access to the project. If you do not provide a specific user login, the Jenkins server must allow anonymous read access for the Jenkins-based widgets to function properly. |
| Jenkins Auth | (Optional) Specify a password for the user to access the Jenkins server. The user must have access to the project. If you do not provide a specific user login, the Jenkins server must allow anonymous read access for the Jenkins-based widgets to function properly. |
Click the widget to view the code coverage information in Jenkins in a new window.
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" |
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:
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.
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 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.
If DTP reads sources from Parasoft code analysis and testing tool reports, make sure that source information is always included by setting the |
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.
Contact your Parasoft representative for additional information. |
| 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 menu. |
| Period | Choose Dashboard Settings to use the dashboard period or choose a time range from the 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 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.
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.
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" |
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.
| 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 menu. |
| Period | Choose Dashboard Settings to use the dashboard date range or choose a period from the menu. |
| Coverage Image | Choose a coverage image from the menu to show coverage data in the widget. See Associating Coverage Images with Filters. |
| Target Build | Choose a build from the menu that contains the data you want to see. |
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.
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" |
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.
| 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 menu. |
| Period | Choose Dashboard Settings to use the dashboard date range or choose a period from the menu. |
| Target Build | Choose a build from the menu that contains the data you want to see. |
| Sort By | Choose an order in which to present the data from the menu. |
| Coverage Image | Choose a coverage image from the menu to show coverage data in the widget. See Associating Coverage Images with Filters. |
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.
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++ Professional C/C++ NextGen
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 and C/C++test NextGen. 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 and C/C++test NextGen can report that plus coverage suppressions. If you are using C/C++ NextGen, the widget you see in DTP will show suppressions in parentheses in the numerator, as shown in the example images above.
When configuring the widget, you can choose the following coverage types:
Refer to the C/C++test Professional and C/C++test NextGen documentation for additional information about coverage types and how to collect coverage.
| 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 menu. |
| Coverage Type | Choose a coverage type from the 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 menu. |
Click on the widget to open the C/C++test coverage report. Refer to the C/C++test Professional and C/C++test NextGen documentation for additional information about reports.
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" |
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 and C/C++test NextGen. 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 and C/C++test NextGen can report that plus coverage suppressions.
When configuring the widget, you can choose the following coverage types:
Refer to the C/C++test Professional and C/C++test NextGen documentation for additional information about coverage types and how to collect coverage.
| Title | Enter a new title to replace the default title that appears on the dashboard. |
|---|---|
| Coverage Type | Choose a coverage type from the 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 menu. |
| Period | Choose Dashboard Settings to use the dashboard date range or choose a period from the 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. |
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 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. If you are using C/C++test NextGen, the "Covered" column as shown in the example above will be "Covererd (+Suppressed)." Refer to the C/C++test Professional and C/C++test NextGen documentation for additional information about reports.
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" |