Thanks for your answer.
I don’t have much experience in SonarQube, so I actually couldn’t understand how unit test success metric can be related to new code period.
Could you please explain a bit more.
And yes, we use “previous version”.
At the moment we added other metrics to QG, unit test failures =0 and unit test errors=0. And it works fine, QG gets failed.
Just I wonder where we made a mistake with Unit test success metric.
yes, there are several Unit tests, that always fail, every build.
As you can see, Quality Gate is failed, just because of one metric - Unit test Failures. But when there was just Unit test success 100%, then Quality Gate was passed, even if there were these 11 Failed unit tests.
I’m confused. First I see a Quality Gate that failed for 2 reasons: duplications and unit test failures. Then I see a metric value list from the left side of the Measures page(?). And then I see … your Quality Gate configuration(?).
Everything you’ve shown here works together AFAICT.
As far as I know quality gate should show all failed metrics. In my case it shows, that quality gate is failed because of 2 metrics and one of them is unit test failures. Question, Why it does not show 3rd failed metric for unit test success 100%? I have failed unit tests, so success is not 100%, it should show me how much % I have passed.
And before that our quality gate was configured differently, there was only one metric for unit tests, we used only unit test success 100% and in that case QG was always Passed, like it doesn’t see that this metric even exist in QG.