SonarQube*@8 tasksThe displaying of the coverage for test projects is different when they are implicitly or explicitly categorized:
Implicitly (reference to NUnit)
Explicit with <SonarQubeTestProject>true</SonarQubeTestProject>:
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?
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.
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.
