New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SonarQube passed ignoring test coverage threshold #905
Comments
Could you please provide your |
Sure. I tried it with this version using pytest:
And using the default test suite like this:
|
Well, I'm confused here. Does the coverage break without sonar cube? Because PyTest Coverage has nothing to do with SQ. |
When I run And when I run the sonar scanner manually with But when I run the sonar-scanner with PyBuilder it reports no quality gate issue. But I think I found the problem. After limiting the sonar-runner only on the src/main/python folder I got no issue there as well, because it only looked for new code and not the missing tests for the already existing code as it seems. So when I added some more new code both ways report issues. |
I'll keep this open as it might be a bug, but I'll need to create a repro case for it. |
Hi all,
today I set up PyBuilder with SonarQube. It works fine. But even though I have not met my test coverage threshold (neither the one stated in PyBuilder e.g. 70 % nor the standard one in SonarQube 80 %). When I just run sonar-scanner outside of the PyBuilder pipeline it notes me that the criteria are violated in SonarQube marking it as a Failure.
It would be great to communicate the threshold from PyBuilder or adjust the used quality gate somehow. Maybe this is already possible and you can tell me how?
The text was updated successfully, but these errors were encountered: