Overview | |
|---|---|
Definition (Hover Text) | is a measurement of the amount of code that is run by unit tests - either lines, branches, or methods |
Source Tools | SonarQube, Sonar Cloud |
Graph type | Multiple Lines |
Filters | Sonar Project |
Hover Format on KPI | Date Range: << Percentage Value>> |
Fields on OverlayExplore |
|
Business Logic | |
Calculation Formula | The calculation is done directly in Sonarqube |
Trend | Higher the percentage, better is the Quality |
Maturity Levels | M1 - <20% M2 - 20-40% M3 - 40-60% M4 - 60% - 80% M5 - > 80% |
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 Unit Test Coverage KPI helps teams improve is a vital metric that aids teams in enhancing code quality, reduce minimizing bugs, and increase boosting development efficiency by assessing the extent to which their code is covered by evaluating the proportion of code that is tested through unit tests. It facilitates This KPI promotes early bug detection of bugs, supports effective refactoring, and enables facilitates the successful implementation adoption of continuous integration and delivery practices. |
...