...
- Parasoft Extension Designer 5.3.2 or higher
- Parasoft DTP 5.3.2 or higher (see Server Settings)
- The following must be configured in DTP:
- At least one filter must be configured to receive Run Configurations from coverage analysis runs.
- Coverage data must be reported to the filter.
- Access to the source code. You can integrate DTP with your source control system or configure the DTP Engines to publish sources to DTP as part of their analysis (default). For details, see Configuring Source Code Views.
- A baseline coverage “image” (a.k.a. the baseline build) should be configured so that comparisons can be made against the baseline. See the following section for details.
Definitions
DTP Project | The root level at which the analysis tools report data. Comes preconfigured with a “filter” that gathers all the Run Configurations that are reported to the project. |
---|
Filter | A DTP configuration that organizes how the data from different analysis runs is displayed in dashboard widgets and reports. |
---|
Run Configuration | A run configuration represents a series of runs (test executions and/or analyses). Runs tagged with the same analysis tool (DTP Engine), DTP project, test configuration, and session tag are grouped into the same run. Run configurations can narrow the data shown for a given filter. |
---|
Build ID | Analysis run metadata that is used to aggregate data across multiple analysis runs into a single “build.” |
---|
...
The following settings are available:
Title | Click in the title field to rename the widget (optional). |
---|
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, the previous build is selected. |
---|
Target Build | Choose the build you want to compare the baseline build to. By default, the latest build is selected. |
---|
...