TQI of an application remains unchanged after decreasing the number of critical violations by excluding the critical violations (objects) and re-generating snapshot.
Release | Yes/No |
|---|---|
| 8.3.x |  |
- Generate snapshot for an application and observe the TQI of the application on dashboard
- Exclude the critical violations (decrease the count)
- Generate the snapshot again and TQI has not been changed
Concentrating on working of a critical rule :
The grade of a rule is based on the ratio between number of defects and number of total object checked. you get a percentage and you will have a grade based on thresholds and this percentage. For a critical rule, the threshold are very hard meaning, to change the grade, it requires to correct ALL violations (or almost) to see a modification of the grade. The aim of a critical rule is to highlight bad practices that have very high risk for the application in production in terms of Business impact.
So, you can exclude 200+ critical violations, if you still have 30 critical violations in the rule, the grade of the rule will not change and so on. Hence, the TQI will not change anymore.
For example, threshold for any critical rule is:
| 99.9899% | to get 4 |
| 99.5% | to get 3 |
| 99% | to get 2 |
| 98% | to get 1 |
Sample: If you have 97% of succeeded checks (or 3% of failed checked that is very low), you will have a grade of 1 !
To change your grade from 1 to 2 or 3 or 4 you are required to correct mainly all defects in your critical rule.
Conclusion:
This is not a bug but normal behavior.
Note
Since TQI is the weighted average. It is expected that the average would decrease if you exclude the rules with a higher/best grades and the average would increase if you exclude the rules with lower grade.
You can observe the behaviour each time by excluding one rule with best grade and one with a low grade the next time.
