...
- Parasoft Extension Designer 5.3.3 or higher.
- Parasoft DTP 5.3.3 or higher.
- A filter must be configured in DTP to receive all types of analysis: Static Analysis, Metrics, Dynamic Analysis (unit testing, functional testing, manual testing), and Coverage. See Associating Coverage Images with Filters.
- The following metrics should be enabled in the code analysis tool (see Metrics Tab for information on enabling metrics and for metrics documentation) for the DTP filter:
- METRIC.MI (Maintainability Index)
- METRIC.NOLLOCIF (Number of Logical Lines in Files)
- METRIC.NOMIT (Number of Methods in Types)
- DTP enables you to constrain how much coverage data is processed. Verify that the coverage image associated with the data you want to process is accepted. See Controlling Coverage Data Processing for Enterprise Pack Artifacts.
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 allows users to pick and choose what data from different analysis runs is used to populate the reports generated in the dashboards. |
| Run Configuration | A Run Configuration is an abstract mapping of various metadata associated with an analysis run (e.g. machine, test configuration, user, session tag, etc). This metadata is used to differentiate the data reported during different analysis runs. It 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” |
You can confirm that the filter and build meet these requirements by checking the Build Administration page in DTP:Anchor build-admin-get-build-details build-admin-get-build-details
...
You can configure the following widget settings:
| Title | You can retitle the widget or use the default title. |
|---|---|
| Filter | Choose Dashboard Settings or a specific filter from the drop-down menu. See Creating and Managing Filters for additional information. |
| Period | Choose Dashboard Settings or a specific period from the drop-down menu. The period is a span of time or code drops. |
| Baseline Build | The baseline build is the first set of data points presented in the widget. You can choose Dashboard Settings, First Build in Period, or Previous Build. |
| Target Build | The target build is the last set of data points presented in the widget. You can choose Dashboard Settings or Last Build. |
| Profile | A profile is required for determining thresholds and how they should be visualized. See Profile Configuration for additional information. |
| Coverage Image | Coverage images are identifiers for the coverage data associated with a test run. See Associating Coverage Images with Filters for additional information. |
| Info | ||
|---|---|---|
| ||
By default, Baseline Build is set to Previous Build and Target Build is set to Latest Build when you configure the widgets. The slice 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 and use an appropriate baseline and target build when configuring the widget as described in the Requirements section. Also see Build Administration. |
...