microsoft / codecoverage

MIT License
79 stars 11 forks source link

Dapper and FakeItEasy are presented as separate projects #78

Closed x-danma closed 9 months ago

x-danma commented 9 months ago

Problem

I have a dotnet api that uses dapper in my api project, and FakeItEasy as a test framwork in my test projects. But those get separate coverage results like so: image

Expected Behaviour

Only my main csproj project (along with the test projects themselves should be covered), not Dapper and FakeItEasy as they are simple dependencies.

Versions

By the way, I got here because of your blog on devblogs.microsoft.com.

fhnaseer commented 9 months ago

Please refer to this scenario to exclude third party dependencies in the coverage report. https://github.com/microsoft/codecoverage/blob/main/samples/Calculator/scenarios/scenario06/README.md

jakubch1 commented 9 months ago

We will probably work on some automatic exclusion as part of: https://github.com/microsoft/codecoverage/issues/72 Closing this one

x-danma commented 9 months ago

Thank you! Scenario6 fixed it!