...
- Parasoft Extension Designer 5.3.2 or higher.
- Parasoft DTP 5.3.2 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 Editing Test Configurations) 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
Scroll Table Layout | ||
---|---|---|
|
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” |
...
Click on a widget after adding it to your dashboard to open the Risky Code Changes drill-down report.
Changelog
Scroll Table Layout | ||
---|---|---|
|
Version | Description |
---|---|
2.0.1 | Performance improvements related to test cases and resources. The coverage tag now appears in the drill-down reports. |
...