Coverage on ... New Lines to cover

[Peteris]

• version - 10.6
• how is SonarQube deployed: Docker
• what are you trying to achieve - just question about one suspicious element

hi
I am devops, not developer so I do not know what is going on inside of java project that I am running sonar analysis on. But there is one suspicious element.

Between two sonar analyses there are over 2400 new lines, but on new code coverage sonar shows:
" Coverage on 113 New Lines to cover"
I understand that those are lines of new code that sonar considers that should be covered by tests… but 113 seems to be somewhat low number considering amount of total new lines.
Is there way to check this number to get confirmation that it is reasonable?

[Colin]

@Peteris

Is there way to check this number to get confirmation that it is reasonable?

Have you checked the new code to see if there are other lines that should be considered for coverage (executable code) that aren’t?

I think there’s no other way than looking at the code being defined as new. If the PR introduces 2000 lines of changes to a GitHub workflow file, or to your actual test files then it makes sense.

You can click on the number of new lines to be taken to a page that shows which files those new lines are in.

[Peteris]

@Colin
Ok thank you