Unit Test Coverage
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 Overlay |
|
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 code quality, reduce bugs, and increase development efficiency by assessing the extent to which their code is covered by unit tests. It facilitates early bug detection, supports refactoring, and enables successful implementation of continuous integration and delivery practices. |
C
© 2022 Publicis Sapient. All rights reserved.