Tech Debt - Sonar Reliability
Overview | |
---|---|
Definition (Hover Text) | Measures the evolution of effort required to fix all detected Bugs in the code. |
Source Tools | SonarQube, Sonar Cloud |
Graph type | Line |
Filters | Sonar Projects |
Hover Format on KPI | Date Range: |
Fields on Overlay | Project Job Name Code Quality Month |
Business Logic | |
Calculation Formula | It is directly calculated in Sonarqube. Sonar Code Quality is graded based on the static and dynamic code analysis procedure built in Sonarqube that analyses code from multiple perspectives. |
Trend |
|
Maturity Levels | M1: E M2: D M3: C , M4: B, M5: A |
Instance level thresholds |
|
Configurations | |
Processor Fields | NA |
Mandatory fields | NA |
How to Validate KPI | |
Suggested ways of working |
|
Sample JQLs |
|
Benefits of KPI | |
How does the KPI help | The Sonar Reliability KPI helps teams improve the reliability of their code by identifying and tracking issues related to error handling, exception management, and other reliability-related factors. It enables teams to prioritize areas for improvement, reduce the risk of bugs and crashes, and enhance overall code quality. By addressing reliability issues, teams can improve customer satisfaction, reduce technical debt, and increase development efficiency. |
C
© 2022 Publicis Sapient. All rights reserved.
This document is being migrated to a new Space starting April 1, 2025. To ensure continued access to documents, please upgrade to the latest version of KnowHOW.