-
Notifications
You must be signed in to change notification settings - Fork 388
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
[BUG] coverlet does not support multiple report formats using CoverletOutput parameter #1610
Comments
Update of GlobalTool.md should be sufficient e.g. whenever more than one coverage format is used in combination with output parameter only a folder shall be used current paragraph
|
This issue is stale because it has been open for 3 months with no activity. |
Describe the bug
coverlet.msbuild.tasks overrides code coverage result file using file name of given CoverletOutput parameter.
To Reproduce
execute command:
dotnet test test\coverlet.core.tests\coverlet.core.tests.csproj --configuration debug /p:CollectCoverage=true /p:CoverletOutputFormat="json%2copencover" /p:CoverletOutput="C:\GitHub\coverlet\artifacts\Reports\coverlet.core\coverage.json" /p:Exclude="[coverlet.core.tests.samples.netstandard]*%2c[coverlet.tests.xunit.extensions]*%2c[coverlet.tests.projectsample]*%2c[testgen_]*" --results-directory:"C:\GitHub\coverlet\artifacts\Reports\coverlet.core" --diag:"C:\GitHub\coverlet\artifacts\log\debug\coverlet.core.test.diag.log;tracelevel=diag"
Expected behavior
2 code coverage result files are available (formats: json, opencover)
Actual behavior
Only one code coverage result file is available.
Configuration (please complete the following information):
Please provide more information on your .NET configuration:
* Which coverlet package and version was used? 6.0.1-preview.39.g9321d2e2cc
* Which version of .NET is the code running on? net8.0
* What OS and version, and what distro if applicable? windows 11
* What is the architecture (x64, x86, ARM, ARM64)? x64
Additional context
none
The text was updated successfully, but these errors were encountered: