# Different coverage visualization of implicitly or explicitly categorized test projects

**URL:** <https://community.sonarsource.com/t/different-coverage-visualization-of-implicitly-or-explicitly-categorized-test-projects/188750>\
**Category:** SonarQube Server / Community Build\
**Tags:** coverage\
**Created:** [September 24, 2026, 11:37am UTC](https://community.sonarsource.com/t/different-coverage-visualization-of-implicitly-or-explicitly-categorized-test-projects/188750 "2026-09-24T11:37:07Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![carlossus](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/carlossus/32/77033_2.png) [@carlossus](https://community.sonarsource.com/u/carlossus)\
**Post date:** [September 24, 2026, 11:37am UTC](https://community.sonarsource.com/t/different-coverage-visualization-of-implicitly-or-explicitly-categorized-test-projects/188750/1 "2026-09-24T11:37:07Z")

</div>

- SonarQube Server Data Center Edition v2026.1 (119033)
- Azure DevOps Integration via `SonarQube*@8` tasks
- C# (.NET10)

The displaying of the coverage for test projects is different when they are implicitly or explicitly categorized:

Implicitly (reference to NUnit)

 ![image](https://europe1.discourse-cdn.com/sonarsource/uploads/sonarcommunity/original/3X/8/8/883810997af0bb61abc333ebdd650a8929d05c71.png)

Explicit with `<SonarQubeTestProject>true</SonarQubeTestProject>`:

 ![image](https://europe1.discourse-cdn.com/sonarsource/uploads/sonarcommunity/original/3X/0/6/066a45520dcea6b78d497aef8cfea513e4943b2e.png)

---

<div class="post-metadata">

**Author:** ![andres](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/andres/32/76342_2.png) [@andres](https://community.sonarsource.com/u/andres)\
**Post date:** [September 28, 2026, 2:45pm UTC](https://community.sonarsource.com/t/different-coverage-visualization-of-implicitly-or-explicitly-categorized-test-projects/188750/2 "2026-09-28T14:45:20Z")

</div>

Hey @carlossus, if SonarQube claims that the project’s coverage is 0%, then I would say that it’s not being picked up as a test project at all, which is strange if you really are explicitly categorizing it. Debug-level scanner logs register some details about project categorization, could you please collect debug scanner logs for both scenarios and share them here?

---

<div class="post-metadata">

**Author:** ![carlossus](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/carlossus/32/77033_2.png) [@carlossus](https://community.sonarsource.com/u/carlossus)\
**Post date:** [September 29, 2026, 1:41pm UTC](https://community.sonarsource.com/t/different-coverage-visualization-of-implicitly-or-explicitly-categorized-test-projects/188750/3 "2026-09-29T13:41:37Z")

</div>

Hi @andres,

I ran the pipeline with implicit and with explicit (`<SonarQubeTestProject>true</SonarQubeTestProject>`) categorization. The logs don’t show any difference (I cannot share them)

Both logs contain same info like

> INFO: Indexing files of module ‘Project.Basic.Test’  
> DEBUG: Test paths: File1.cs, File2.cs  
> INFO: Excluded sources: \*\*/_.py, \*\*/_.java, \*\*/_.xml, \*\*/_.xaml, \*\*/_.yml, \*\*/_.csproj, \*\*/_.sln, \*\*/_.slnf, \*\*/_.cu, \*\*/_.ptx, \*\*/\*.g.cs,  
> DEBUG: ‘/.Basic.Test/File1.cs’ indexed as test with language ‘cs’  
> DEBUG: ‘/.Basic.Test/File2.cs’ indexed as test with language ‘cs’

and

> DEBUG: Adding file type information (has MAIN ‘false’, has TEST ‘true’) for project ‘Project.Basic.Test’

Only the `ProjectInfo.xml` has a difference. When running with implicit categorization, it contains `<ProjectType>Test</ProjectType>`, with explicit categorization it doesn’t have this entry.

---

<div class="post-metadata">

**Author:** ![andres](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/andres/32/76342_2.png) [@andres](https://community.sonarsource.com/u/andres)\
**Post date:** [September 29, 2026, 2:15pm UTC](https://community.sonarsource.com/t/different-coverage-visualization-of-implicitly-or-explicitly-categorized-test-projects/188750/4 "2026-09-29T14:15:06Z")

</div>

Hey @carlossus, thanks for the insight, I do understand that you can’t share the logs. The `ProjectInfo.xml` difference is interesting and at this point I’m starting to feel like it might indeed be a bug… I will flag this for the devs, if the issue is as easy to reproduce as it seems, they probably won’t need to see any additional logs or files.