-
Notifications
You must be signed in to change notification settings - Fork 0
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
blog/code-coverage-vs-2019-coverlet #5
Comments
Previously I found it difficult to try to get coverlet working. This article really clears it up and makes it simple to add/use coverlet. |
Glad to hear that! |
Hi, I'm the author of the Run Coverlet Report extension. Thanks for blogging about it ! |
Glad you liked it! Is there anything else I could add? :) |
Great article, thanks a lot for it! |
Great summary, thank you! I found one caveat: the dotnet tool commands use my nuget configuration, but only the first entry. I resolved by creating a temporary nuget config file like this
named it NuGet2.config Hth. |
This is just the perfect article I found. |
This helped me out quite a bit but I was wondering if you could publish the steps on how to add coverlet reports to the github yaml files so I can add coverage to my current build workflow |
First of all, it's a great article and it helped me a lot. Thanks for the article. I leave here my contribution. I was using it in VS 2019 without any problems, but in VS 2022 it stopped working, after a search I found that .Net had a bug covering up to SDK version 7.0.101. After updating the SDK, everything is working perfectly again. Including using "Integration Type" as MSBuild". |
Tried in VS 2022 Preview - does not work -
|
@vsix27, I suppose it's just because some tests are failing. |
How to view code coverage with Coverlet and Visual Studio 2019 | Code4IT
Code coverage is an indicator of the quality of your code. With Coverlet and VS2019 you can have a human readable report to see where to improve your code.
https://www.code4it.dev/blog/code-coverage-vs-2019-coverlet
The text was updated successfully, but these errors were encountered: