Hi Ernesto,
This is very similar in nature to the thread you started yesterday. Just because you didn't get an immediate answer, that didn't mean you weren't going to get one. In general, you should probably wait at least 3 or 4 days, and then you should bump the existing thread, rather than starting a new one. That's because this group isn't just for your immediate gratification but for posterity as well. Also (while I'm griping) your screenshots are huge. I had to expand my browser window to full screen width to be able to see them, which makes me less inclined to fool with the thread. No idea whether I'm the only one on that, but in general, you'll "help us help you" if you focus both text and screenshots on the problem.
Okay, now that I've got that off my chest, I'm prepared to try to be helpful. :-)
There are a couple things going on here.
First, your Quality Gate:
You've got redundant conditions in the Quality Gate:
- Coverage Over Leak Period is less than 70
- Coverage on New Code is less than 70
We're aware that this is confusing and plan to handle it. In the meantime though, you probably want to remove one of these. I'd vote for "Coverage Over Leak Period" just because "Coverage on New Code" is more explicit.
You've also got a condition on Line Coverage. That's a slightly a different thing, but still overlaps with the first two. Just FYI.
You've also got Uncovered Lines Over Leak Period is less than 5. I think that's probably not what you meant. Instead, you probably meant to alert when Uncovered Lines Over Leak Period is greater than 5. However, "5 lines" seems like a rather unforgiving threshold to me, and one that gets harder to meet the more changes there are in the leak period. That's why we use and recommend percentage metrics for quality gate thresholds. If it were my quality gate, I'd drop this condition.
Now let's talk about your quality gate failures. You keep sending screenshots with arrows pointing at your all-time coverage percentage. But your quality gate doesn't test all-time coverage. It tests (in multiple ways) coverage in the Leak Period. So your arrows should be pointing to the numbers in the yellow blocks on the right of the screen. Moved over, you'll find they're pointing at "-", a.k.a. the 0% that's showing up in the Quality Gate section of the page.
So now you've got numbers that match up from one place on the screen to another. Yay. But why, with no changes, is your quality gate failing? I suspect this has something to do with the fact that this project is brand new in SonarQube. Once you start touching code (and writing tests for it!) this should normalize.
Ann