-
The `dotnet-coverage` tool today supports multiple coverage output formats and output files when using a comma-separated list in the `-f, --output-format` argument . This works even if it is not a wel…
-
Hi and thanks for a great project.
When running the following `dotnet test` command, and any test fails, then no coverage report will be written. If your action cannot find a coverage report (cove…
-
### Installed product versions
- Visual Studio: 2019 Professional (16.10.0)
- This extension: 1.1.141
### Description
I have couple tests that take values from registry. Thus, they require 64bit…
-
## Note
Issues in this repo are for tracking bugs, feature requests and questions for the tasks in this repo
For a list:
https://github.com/Microsoft/azure-pipelines-tasks/tree/master/Tasks
…
-
Hi
I'm in the process of migrating projects to .NET Core 6 from .NET Framework 4.7.2.
I've encountered problem that `System.Windows.Forms` could not be loaded when tests referencing such library…
-
Thanks for creating ReportGenerator! I think it provides a great overview of code coverage and I really like all the integration options.
I got however a bit confused about all the options to use i…
-
Hey @jonesbusy,
this plugin depends on the code-coverage-api-plugin plugin, which is deprecated and end of life in favor of https://github.com/jenkinsci/coverage-plugin#jenkins-coverage-plugin.
…
-
when build found the following errors with ver 6.0.1 and. netcore6.0:
```
Unhandled exception. System.ArgumentException: Type Coverlet.Core.Enums.ThresholdStatistic cannot be created without a custo…
-
Get a null pointer exception during import opencover report, v.1.0.3
```node {
st…
-
This is the same issue as [OpenCover issue #615](https://github.com/OpenCover/opencover/issues/615) -- the compiler generates many functions (such as comparison operations) which show in the IL but no…