No coverage data due to path problems (?)

[mactemp-pro]

So basically, I have installed the newest version of FCC on VS 2022 and trying to use it for unittests with Google Test. I am using TAfGT, which comes pre-installed and Microsoft.googletest.v140.windesktop.msvcstl.static.rt-dyn from NuGet. Normal testing with VS' build-in Test-Explorer works, but FCC has a problem. In Cobertura.xml there's a path, that isn't related to my project, but gives me errors like "File 'D:\a_work\1\s\GoogleTestAdapter\Core\GoogleTestDiscoverer.cs' does not exist (any more)." I found nothing about this topic online, so here am I.

[tonyhallett]

I am not too sure that these are errors, I think they are just notifications.

Are you runnung with RunMsCodeCoverage Yes ?

If you are then you will need to add a minimal repro so it can be investigated.

[tonyhallett]

Is TAfGT is https://github.com/microsoft/TestAdapterForGoogleTest ?

Perhaps you can try https://www.nuget.org/packages/GoogleTestAdapter/ - I am not sure how this relates https://www.nuget.org/packages/Microsoft.googletest.v140.windesktop.msvcstl.static.rt-dyn

[kirill-slk-hs]

Hello, I'm having the same issue. I have tests project and tested project and no matter if RunMsCodeCoverage is enabled or not, I cant get the coverage for the target project. Target project is exe and is referenced by a test project. With cobertura, the target assembly doesnt show up in the report at all, with MsCodeCoverage it shows the target assembly in the report, but with 0 testable lines.

[tonyhallett]

@kirill-slk-hs - same setup ?

[kirill-slk-hs]

I have the other project with exactly the same approach, and they are working fine. Test coverage shows for the all referenced assemblies. The only difference is in the naming convention. Wherever test project is named adter target project + ".Tests" it works. The solution I have problem with has different namings for tested and testing projects

[kirill-slk-hs]

I have ASP.NET web app

[kirill-slk-hs]

I tried inclusions, different modes and configurations. The best I could achieve is with MsCodeCoverage, is that assembly is showing up in the report, but files "do not exist (any more)" and testable lines count is 0

[kirill-slk-hs]

Please let me know if I can provide more specific info

[tonyhallett]

I have ASP.NET web app

So a different setup

[tonyhallett]

@kirill-slk-hs

You need to create a new issue with a minimal repro.