SonarCloud incorrectly flagging code covered by unit tests

[Roberto_sonar (Roberto)]

• ALM used: GitHub
• CI system used: GitHub actions
• Scanner command used: dotnet sonarscanner begin /k:“PROJECT_KET” /d:sonar.token=$SONAR_TOKEN /d:sonar.scanner.scanAll=false
• Languages of the repository: C#

Hello

We have SonarCloud incorrectly flagging as uncovered code that is actually covered; please see attached screenshots

Can you please clarify/advise why we see this discrepancy?

Regards,

Roberto

[Colin]

What do your analysis logs say about the import of code coverage?

How to find logs about importing code coverage

When coverage data isn’t appearing as expected in SonarQube Server / Community Build or SonarQube Cloud, the first place you should look is the scanner logs. Where do I find the scanner logs? This will likely be broken out into its own guide soon The Scanner logs are the output of executing one of the scanners, either directly or wrapped by one of many integrations, such as the SonarScanner for Jenkins, SonarScanner for Azure DevOps, SonarQube/SonarCloud GitHub Actions or SonarQube /…