-
Notifications
You must be signed in to change notification settings - Fork 386
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Missing coverage in 1.7.0 #852
Comments
Do you have |
We do have exclude tags elsewhere in the project. Those seem to have been handled correctly. It just completely lost whole controller methods. I'll try to work up an example when I have a moment. |
Also can you try to use collectors integration?Msbuild and .net tool at the moment suffer of some issue related to vstest behaviour https://github.com/coverlet-coverage/coverlet/blob/master/Documentation/VSTestIntegration.md |
I updated the coverlet.collectors to the latest version and I'm hitting some issues. The report in the VSTS reports that most of the async methods are |
@askpt can you attach your command line?Could be an issue with some attribute filters maybe. |
@MarcoRossignoli sure! Here is my runsettings:
VSTS Task:
|
You cannot use dup of #794 (comment) |
@JustinBerger any news? |
Closed for stale conversation, feel free to re-open if needed. |
In a .net core project running using coverlet.console 1.6.0 we get these results.
But when running in 1.7.0 (and 1.7.1) we get
Running on windows with this command
coverlet .\tests\UnitTests\bin\Debug\netcoreapp3.1\namespace.UnitTests.dll --target "dotnet" --targetargs "test .\tests\UnitTests --no-build" --format opencover --output "c:\dev\coverage\namespace\" --exclude '[coverlet.*]*' --exclude '[NUnit3.*]*' --exclude '[Refit]*' --exclude '[StackExchange.*]*' --exclude '[Refit.*]*' --exclude '[System.*]*' --exclude '[Pipelines.*]*' --include '[*]*'
When we run Report generator against the opencover report, it shows whole methods as if they were set to ignore coverage, rather than being uncovered.
The tests cover those methods (though not completely).
I don't yet have a sample app I can reproduce the results with.
The text was updated successfully, but these errors were encountered: