Keep code coverage non decreased after pull requestes

[Sergey_Ovchinnikov]

SonarQube Developer Edition Version 8.7.1 (build 42226)

Hello Experts!
We would want so SonarQube fails the build if Overall Code Coverage is being decreased after a pull request.
The goal is to have non decreasing code coverage in the project. It should be the same or grow.
Such approach works good for legacy products.

Example:
Before a pull request project has 50% of code coverage.
If after this pull request Overall code coverage becomes 51% or more - build OK, if it becomes 49% or less - build fails.

At my previous job it was possible to do in SonarQube (years ago)
At the current version I cannot find how I can do it. Conditions have no such options.

1. Please tell is it possible?
2. If not, why it was removed from the previous version of SonarQube?

I have found a couple of topics regarding this issue but they do not answer on my question:

Fail Quality Gate if the code coverage after merge will decrease on master

For each MR, we don’t want it calculate code coverage on the incremental code, instead, we want to compare the code coverage of current long-live branch (in most cases, master), and the code coverage after merging a MR to the master. For example, say Master branch has a overall 73.41% coverage, and we created a MR from feature-branch-1 to master. We expect sonarqube to calculate the code coverage after feature-branch-1 is merge to master. And if that value is smaller than 73.41%, we expect the …

How to set quality gate on PR based on estimated after merge

I know we can have quality gate based on coverage but that’s a hard coded value. What I want to enforce is it that the total code coverage should not decrease. For example I set the QG on coverage to be > 50% on new code. PR A increased the total coverage to 55%. Now PR B should be checked to have coverage > 55%, meaning it should not decrease the coverage from it’s current value. I hope I’m clear enough. I’m using SonarQube version 8.1.

Ratcheting Quality Gate conditions: Fail Quality Gate if coverage decreases from last analysis

SonarQube version: 7.9.1 LTS sonar.leak.period = previous_version We want our Quality Gate to fail if coverage decreases during the leak period, regardless of whether it is still above our threshold of 70% (Example: If coverage from last analysis was 75%, quality gate should fail if coverage on next analysis is 74.9% or lower). In older versions of SonarQube this could be accomplished by using the condition “Coverage, Delta since last analysis, less than, 0”. Is there a way to do that with t…

[ganncamp (G Ann Campbell)]

Hi,

Exactly what you describe isn’t possible. What is possible is to enforce coverage on new code. Make sure that new code is always covered and organically over time your overall coverage will naturally increase.

If you want to enforce this strictly, you’ll need to disable ‘Ignore duplication and coverage on small changes’ (Administration → General).

 
HTH,
Ann

[Sergey_Ovchinnikov]

Hello Ann!
Thank you for the answer.
This flag means that SonarQube will check on duplication and code coverage even on small pieces of code (less than 20 lines).
Does it mean that even when this flag is ON the SonarQube automatically checks New Code on duplications and code coverage when lines more than 20?
It actually means that SonarQube already does this action. So it fails New Code when code coverage is not enough.
But what I see, that even when New Code build fails the Overall Code build is OK. And that’s the issue. In other words, we do allow a Team to decrease the Overall Code coverage.

Whether my understanding it correct or I misunderstand?

Thank you in advance.

[ganncamp (G Ann Campbell)]

Hi,

SonarQube will always calculate those things on new and overall code. What the flag does is determine whether the result of the the calculation will fail the Quality Gate for small changesets.

 
HTH,
Ann