Quality gate passed, even when the coverage didn't pass the threshold

SonarQube Cloud
, ,
1

Template for a good new topic, formatted with Markdown:

Quality gate is set to be 60% for new code

image
image1381×665 57.3 KB

But this one clearly passed with 33% coverage. Don’t know what happened here

image
image1456×351 45.6 KB

2

Hello Rajesh and welcome on the community forum!

Actually on very small PR when there is less than 20 lines of code the coverage condition and duplication condition on new code are ignored to compute the QG.

And as you can see, this is what happen in your case:

image
image1183×220 25.5 KB

1 Like
8

Hello @Gregoire_Aubert @ganncamp I see that a ticket which has been raised for giving capability to customers to turn off no code coverage check or duplicate check for less number of new lines of code (<20) has been closed as fixed. Here is the ticket [SONAR-10485] Provide a way to always enforce coverage and duplication Quality Gate conditions - SonarSource

We are using Sonar cloud, private project and I am not able to see this option. Could you clarify below queries

  1. Is this feature now part of 8.9LTS
  2. Is this feature rolled out for SonarCloud
9

Hello Ajith,

It hasn’t been implemented on SonarCloud for the time being, you can track the ticket for SonarCloud here: [SCCOMM-41] Provide a way to configure the Quality Gate fudge factor - SonarSource

And in SonarQube, it’s part of the 8.9LTS indeed.

10

Thank you @Gregoire_Aubert

I have upvoted the ticket you shared [SCCOMM-41] Provide a way to configure the Quality Gate fudge factor - SonarSource. But couldn’t add any comment to the ticket you shared. Just wanted to add this has been fixed as part of Sonar 8.9LTS already ([SONAR-10485] Provide a way to always enforce coverage and duplication Quality Gate conditions - SonarSource) and may be a low hanging fruit. What is different about both the tickets one starting with SONAR- and another SCCOMM- in Jira?

11

Thanks, I added a link to the SONAR ticket.

The difference between the two kind of tickets is that SONAR- tickets are related to the SonarQube product and SCCOMM- tickets are related to the SonarCloud product. They have different backlog and teams working on them.

13

Thanks @Gregoire_Aubert. I hope this gets picked up soon.

14

@Gregoire_Aubert - any idea when this is going to be picked up? This setting is a problem for the ideal happy path where a change takes only a few lines of code.