And what I notice is that your default coverage reporting shows 0% coverage in all three columns… just like SonarQube. To me the first interesting question is how you can have a 14.28% coverage with a total of 0%. Seems like a div-by-zero error waiting to blow up.
First of all, thank you for your interest.
I added a test project to Solution and this is how it comes up in the reports.
Below I share a test result that covers other projects.
I don’t understand the result.
Just to be sure, if you click on the 0% in your homepage, it gives you a worst-first list of file coverage. If you scroll to the bottom, does every single file have a 0% next to it?
Did you add that marking at the file level or just within files to exclude only parts of them?
SonarQube doesn’t read that markup. So if you’ve it to exclude an entire file from your coverage engine, then your coverage report won’t include that file & analysis will proactively count it as 0% covered. (Here’s why.) If you’ve only used it to exclude a subset of the file, then the file will be included in your coverage report and SonarQube go off what the report say.
Hi Ann,
I’ve added the relevant code at the class level.
After this addition, the results in the report have changed.
But when it sends it to sonar, it still shows 0.
When I try .net Core 5.0 in an empty project. After updating some libraries, report flow was provided to Sonar Portal. Is it a version problem?
The following is the content of the current Test project