...
For each of these, SQ reports the number of flaws, a rating (from A to E, with A being the highest / "best" score) for this characteristic, and a link to a trend diagram. Each of the reported information can be clicked and directs the user to more detailed analysis and/or diagrams for this value. The definition of the ratings as provided by SQ is described in the Rating table below (as well as, in more detail, at the official SQ documentation).
| Table Filter |
|---|
| inverse | false |
|---|
| ddSeparator | |
|---|
| sparkName | Sparkline |
|---|
| hidePane | Table header |
|---|
| isNew | false |
|---|
| separator | Point (.) |
|---|
| labels | Maintainability rating |
|---|
| default | |
|---|
| ddOperator | |
|---|
| cell-width | 150 |
|---|
| userfilter | Maintainability rating |
|---|
| datepattern | yy-mm-dd |
|---|
| id | 1643214224199 |
|---|
| isOR | AND |
|---|
| formatVersion | 2 |
|---|
| order | 0 |
|---|
|
| Reliability rating | Security rating | Maintainability rating |
|
|---|
| no bugs | no vulnerabilities | technical debt ratio is less than 5% |
| | at least one minor bug | at least one minor vulnerability | technical debt ratio is less than 10% |
| | at least one major bug | at least one major vulnerability | technical debt ratio is less than 20% |
| | at least one critical bug | at least one critical vulnerability | technical debt ratio is less than 50% |
| | at least one blocker bug | at least one blocker vulnerability | technical debt ratio is higher than 50% |
|
|
SQ reports separately the overall numbers and the values for new code (i.e., for the code developed since previous analysis in SQ). That helps in getting the general insight into the project status, and tracking the trends.
...
