Code Violations
Overview | |
---|---|
Definition (Hover Text) | highlight count of issues that exist every time a piece of code breaks a coding rule. The set of coding rules is defined through the associated Quality profile for each programming language in the project |
Source Tools | SonarQube, Sonar Cloud |
Graph type | Line |
Filters | Sonar Project |
Hover Format on KPI | Date Range: Blocker: <<Value>> Critical: <<Value>> Major: <<Value>> Minor: <<Value>> Info: <<Value>> |
Fields on Explore | Project Job Name Sonar Violations Weeks |
Business Logic | |
Calculation Formula | Its directly calculated in Sonarqube |
Trend | Higher the violations, lower is the Quality |
Maturity Levels | - |
Instance level thresholds | - |
Configurations | |
Processor Fields | NA |
KPI Specific fields | NA |
How to Validate KPI | |
Suggested ways of working |
|
Sample JQLs |
|
Benefits of KPI | |
How does the KPI help | The Sonar Violation KPI is a valuable tool for teams aiming to enhance code quality. It identifies and monitors violations of coding standards and best practices, facilitating early detection of potential issues. This proactive approach not only reduces technical debt but also improves the maintainability of the codebase. By systematically addressing these violations, teams can elevate overall code quality, minimize bugs, and boost development efficiency. |
© 2022 Publicis Sapient. All rights reserved.