Condition coverage metric is inaccurate (SQ LTS 9.9)

  • which versions are you using: SonarQube Developer Edition
  • how is SonarQube deployed: Docker
  • what are you trying to achieve: get accurate metrics
  • what have you tried so far to achieve this: simple scanning

Description of a problem
Even though the line within the condition body is not covered, which means one of the possible true/false flags was not covered, both Conditions to cover and Uncovered conditions = 0

Hey there.

Something already seems funny with the reports being passed to SonarQube.

I would suggest looking into this first, and then see if the problem persists around condition coverage.

Hey, Collin,


I believe you wanted to refer this issue, did not you? (I see the link to this same question).

We are using GO. Do I understand correctly that SonarQube generates conditions coverage metrics based on the unit-tests reports passed to the Sonar instance? Do you think there is a chance SQ does not process those correctly? I’d like to ensure the problem is on our/Go side.

Hey there.

Yes, I meant to link to your other post! Sorry about that.

Thanks for the clarification that you’re using Go. It reminds me of an issue with Go Coverage specifically because of the information in the report. You can find details of the work (already deployed) at SONARSLANG-537

Would it be possible for you to create a small project that reproduces this issue on just one file? It would speed up the investigation a lot, and it looks like you might already have a source file / tests written