ALM used : Azure DevOps CI system used : Azure DevOps All of this is run inside of docker, I’ve tried both locally and through Azure DevOps Pipelines Scanner command : dotnet sonarscanner begin \ /k:"<projectName>-opf" \ /o:"<orgName>" \ /d:sonar.token="${DOCKER_SONAR_TOKEN}" \ …

So after making our branch a long-lived branch we were able to get the code-coverage percentage to actually change.. So that’s great. It seemed that the test-libraries included in our scan was from packages that we use, so those are fine to cover as well. I think a lot of my problems were about n…

Hey there! What do the logs say about importing code coverage? [image] How to find logs about importing code coverage Guides When coverage data isn’t appearing as expected in SonarQube Server / Community Build or SonarQube Cloud, the first place you should lo…

Hi, thanks for your reply! [image] I’m not entirely sure what I am looking for, but here is what I’ve found. [image] [image] I have a feeling it might be this: [image] Which means I need to get a better overview of the folder structure I think

I’ve come one step further, but I need some help figuring out what to do next. #30 21.90 10:32:40.487 INFO: Sensor C# File Caching Sensor [csharpenterprise] (done) | time=25ms #30 21.90 10:32:40.488 INFO: Sensor C# Tests Coverage Report Import [csharpenterprise] #30 21.90 10:32:40.488 DEBUG: Analyz…

It looks like whatever coverage file is being picked up includes entires for, inexpclicably, the source code of vstest! Have you confirmed that this coverage file actually contains entries pertaining to your source code? [image] Stine: #30 21.91 10:32:40.490 DEBUG: Pattern matcher returns a si…

You are right, how can this be?? When running the tests in the dockerfile it lists successful tests from our unit test project. I can’t figure out how to troubleshoot this further

Here is an output from the pipeline run: [image] A report is generated, and the redacted text is my project name, so I see that it does pick up some files from the project

@Colin Is there a way to run a sonar scan on a short lived branch but still get a FULL scan of the entire repo? I’m finding it hard to actually see any change from run to run, and with the “There is not enough lines to compute coverage” I cannot really test if my setup is correct without merging to …

@Stine Sounds like you want to run a long-lived branch analysis (docs on Adjusting the long-lived branch name pattern of your project ) This will execute a “full” analysis without requiring you to merge to main.

@Stine if I distill one additional takeaway here, I think it would be best if we showed the estimated coverage here even when there are no new lines to compute coverage on [image] I’ll flag that for our team

YES! I think a lot of the threads here would not exist if that was a feature! Excellent suggestion!

No code-coverage reported

SonarQube Cloud

Colin (Colin) May 7, 2025, 7:33am 2

Hey there!

What do the logs say about importing code coverage?

I’ll make sure to include the docs for .NET Test Coverage just in case.

Topic		Replies	Views
Dotnet project showing code coverage 0% - Azure DevOps SonarQube Cloud coverage	5	571	July 4, 2024
Unable to get code coverage for one of the dotnet project in sonar cloud SonarQube Cloud coverage , dotnet6 , sonarqube-cloud	4	657	June 16, 2023
Issue with code coverage not displaying SonarQube Cloud coverage , dotnet	1	120	July 22, 2025
Azure Devops - No Coverage - C# .net SonarQube Cloud coverage , sonarqube-cloud	4	2048	May 15, 2023
SonarQube 10.6 .NET coverage - still none SonarQube Server / Community Build azuredevops-services , coverage , dotnet	4	250	July 10, 2024

No code-coverage reported

Related topics