This tutorial describes how the Static Analysis vs Coverage example flow gathers newly-introduced violations and correlates them with the coverage data in the same resource. Violations are prioritized to reflect their potential risk based on the coverage data and a configurable coverage threshold. The Risk/Impact for the violations will be set to one of the following values:
| Scroll Table Layout | ||
|---|---|---|
|
| Extreme | File has no coverage |
|---|---|
| High | File has low coverage (coverage under the specified threshold) |
| Low | File has acceptable coverage (coverage at or below the specified threshold) |
...
After the module coverage data has been obtained and the violations are filtered, the violations are grouped by projectResourcePath. This parameter represents the file containing the violation. For each set of violations, file coverage for the projectResourcePath is obtained and the set of violations is passed to a DTP REST API node so that the Risk/Impact can be set for the entire set of violations.