Coverage file has odd directories in Module data

[ghost]

Good afternoon, all,

We are having some issues with code coverage analysis of a .Net Framework project. We are using opencover to generate the coverage xml file, which is then subsequently uploaded to SonarQube for reporting.

In the coverage xml file produced, there are tags. Under that tag is a tag, with multiple tags. Each tag has an attribute called fullPath, which is set to a file path. When we run an analysis of the coverage file, we are getting missing file reports for the file paths specified for the fullPath attribute. I've used both SonarQube and the reportgenerator project (https://github.com/danielpalme/ReportGenerator). Both report the missing files.

The Module being referenced is a module pulled via NuGet that was built as part of another project, and uploaded to our local NuGet repository. The file paths shown in the aforementioned fullPath attribute don't exist on my local system, and so they are not going to be found.

Where do those file paths come from?

The problem that we're having is that we are getting erroneous coverage data from SonarQube when this coverage file is analyzed. Sonar support says it has to do with these missing files, so I'm trying to track down where those file paths come from. An example of the errors being reported in the SonarQube log is:

11:11:21.748 DEBUG: OpenCover parser: Skipping the fileId '1', line '448', vc '1' because file 'D:\repos\NUnit\nunit3-vs-adapter\src\NUnitTestAdapter\AdapterSettings.cs' is not indexed or does not have the supported language.

I'm not even sure why it's trying to find an NUnit file.

Note that I am not the author of the code, nor of the components involved in this project. I'm just to one tasked with supporting this part of our ci-cd pipeline, and people come to me when they have issues. I'm sure some of you have been in that position before.

I'd appreciate any input on this.

Morgan Vergara