Page History

...

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"

...

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"

...

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"

...

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"

...

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"

...

• 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. 

  Info
  title 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 Test 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.

...

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.  

...

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.

...

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"

...

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"

...

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"

...

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"

...

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"