Skip to content
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

Coverage file default location #44449

Open
aelij opened this issue Jan 21, 2025 · 0 comments · May be fixed by #44522
Open

Coverage file default location #44449

aelij opened this issue Jan 21, 2025 · 0 comments · May be fixed by #44522
Assignees
Labels
dotnet-fundamentals/svc in-pr This issue will be closed (fixed) by an active pull request. ⌚ Not Triaged Not triaged

Comments

@aelij
Copy link

aelij commented Jan 21, 2025

Type of issue

Missing information

Description

The article specifies that we can use the --coverage-output parameter to specify where the output is saved, but doesn't say that if unspecified, the file name will be under --results-directory with a random (GUID) file name and a default extension according to the --coverage-output-format parameter (.coverage, .xml and .cobertura.xml, respectively).

Additionally, it doesn't say the default format is 'coverage'.

Page URL

https://learn.microsoft.com/en-us/dotnet/core/testing/unit-testing-platform-extensions-code-coverage

Content source URL

https://github.com/dotnet/docs/blob/main/docs/core/testing/unit-testing-platform-extensions-code-coverage.md

Document Version Independent Id

2a4c1d53-73c0-8532-3903-59f78e09c784

Article author

@Evangelink

Metadata

  • ID: b7d643d0-0a87-627d-58ae-aeac2facce45
  • Service: dotnet-fundamentals

Related Issues

@dotnet-policy-service dotnet-policy-service bot added the ⌚ Not Triaged Not triaged label Jan 21, 2025
@Evangelink Evangelink self-assigned this Jan 25, 2025
@Evangelink Evangelink linked a pull request Jan 25, 2025 that will close this issue
@dotnet-policy-service dotnet-policy-service bot added the in-pr This issue will be closed (fixed) by an active pull request. label Jan 25, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dotnet-fundamentals/svc in-pr This issue will be closed (fixed) by an active pull request. ⌚ Not Triaged Not triaged
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants