In this chaptersection:
| Table of Contents | ||
|---|---|---|
|
...
Risky Code Changes calculates metrics associated with code changes and displays them DTP widgets and reports. Risky Code Changes derives three different metrics on a per file basis:
- test Test score
- maintainability Maintainability score
- risk Risk score
The metrics are derived according to the following calculations:
...
- If you have not already done so, install the Process Intelligence Pack.
- Open Extension Designer and click the Services tab.
- Expand the Process Intelligence Engine service category. You can deploy assets under any service category you wish, but we recommend using the Process Intelligence Engine category to match how Parasoft categorizes the assets. You can also click Add Category to create your own service category (see Working with Services for additional information).
- You can deploy the artifact to an existing service or add a new service. The number of artifacts deployed to a service affects the overall performance. See Extension Designer Best Practices for additional information. Choose an existing service and continue to step 6 or click Add Service.
- Specify a name for the service and click Confirm.
- The tabbed interface helps you keep artifacts organized within the service. Organizing your artifacts across one or more tabs does not affect the performance of the system. Click on a tab (or click the + button icon to add a new tab) and choose Import from the vertical ellipses menu.
- Choose Local> Flows> Workflows> Process Intelligence> Local > Flows > Workflows > Process Intelligence > Risky Code Changes and click Import.
- Click anywhere in the open area to drop the the artifact into the service.
- Click Deploy to finish deploying the artifact to your DTP environment.
- Return to DTP and refresh your dashboard. You will now be able to add the related widgets.
...
The demo profile is a fully - configured example that includes three risk level thresholds:
- lowLow
- medium Medium
- highHigh
See Working with Model Profiles for information on configuring model profiles.
...
| 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 Configuring 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. |
...
Risky Code Changes - Pie Chart
This widget shows widget shows risky code change aggregates (e.g.for example, the number of files that fall into the various risk levels defined in the profile).
...
The Test Deficit column shows the number of tests covering the file, the number of methods used in the metrics calculation, and the level of code coverage. A Test Deficit score is calculated based on these values. You can perform the following actions:
- Click on the Tests link to view the tests in the the Test Explorer.
- Click the Methods link to view the methods in the Metrics Explorer.
- Click the Coverage link to view the code coverage for the file in the Coverage Explorer.
The Quality Debt column shows the number of severity 1 and 2 static analysis violations, number of test failures, and the Logical Lines of Code score. A Quality Debt score is calculated from these values. You can perform the following actions:
- Click on the Test Failures link to view the tests in the the Test Explorer.
- Click the Logical Lines of Code link to view the methods in the Metrics Explorer.
...