- We are using SonarQube DataCenter edition v9.9.6 (build 92038)
- SonarQube is deployed via helm
In our dotnet projects, we are excluding some files from coverage. Basically, files that cannot be unit tested, like connection to db. For that, we use the [ExcludeFromCodeCoverage] attribute that is built-in. That attribute can be put at the class/file level or at the assembly/project level.
We are currently using the one at the file level because it is the only one that works. The issue with that is we need to provide it each time, so a decision that stays at the developer level. So to make things simpler, we want to isolate those “db” classes in an assembly and exclude the whole assembly. But right now we cannot because of a sonarqube limitation.
We checked the generated coverage report, everything looks fine, the assembly is flagged as excluded in the xml, but in sonar, it is acting weird:
- If the excluded assembly doesn’t have a test project and is not referenced by any other project, we have a correct behavior: no coverage to report on all files in that project
- If excluded assembly does have a test project, files that are not tested are are fine (they don’t have a coverage report). But the few files that have tests show 0% coverage (although lines are covered). Tests on these files make sense to ensure that nothing is broken (and in some cases can even be 100% covered)
- If excluded assembly doesn’t have a test project but is referenced by another project, some files don’t have a coverage (as expected), but files that are used in test files of other projects show 0% coverage.
And again, if we exclude the files one by one, we don’t have this weird behavior, but we want to organize the code and isolate those uncoverable files into one assembly and not have the developer worry about which files should be excluded and which files should not be excluded.