Not check coverage on new code

[asd_asdasd]

Hi,

We have a new PR that doesn’t show the code coverage on Sonar. Even though we set the quality gate with coverage = 50%, the PR still passed without coverage.

As per the screenshot, you can see there is 0% coverage on 9 new lines to cover, and none of them are excluded from the exclusion list.

[asd_asdasd]

@Colin Could you pls take a look at this? we got a lot of PRs which is passed the Sonar gate without matching the gate condition.
Is there any change in SonarCloud that could lead to this issue?

[Colin]

Hey there.

Please don’t tag individuals not already involved in the thread. You might think it bumps it to the top of our list, but it actually puts it on the bottom.

Take a look at our FAQ

[asd_asdasd]

Sorry @Colin, but our issue is quite urgent. It breaks our quality control.

[Colin]

Thank you.

Please have a look at this post:

Default Quality Gate Isn't Functioning As Expected

Hey there. Conditions on Coverage/Duplication are not calculated when there are fewer than 20 lines (SONAR-9352). We did this because of our own experiences with “diminishing returns” situations where the cumulative change sets were small and one or two uncovered lines caused the project to fail the Quality Gate. So a few things to note: I (think) we have lost something in the UI that is supposed to tell you this when your SLB falls into this situation. Something like: “Some Quality Gate con…