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 can be merged with dotnet-coverage tool #1656

Closed
tillig opened this issue May 17, 2024 · 0 comments
Closed

Coverage can be merged with dotnet-coverage tool #1656

tillig opened this issue May 17, 2024 · 0 comments
Assignees
Labels
documentation Solved The issue is solved and can be closed

Comments

@tillig
Copy link
Contributor

tillig commented May 17, 2024

Currently in the docs it directs folks trying to merge coverage reports to look at a comment from 2020 with some Powershell script to help merge coverage reports.

Since then, the dotnet-coverage tool has been released and allows you to merge coverage reports pretty easily.

For example, if your coverage reports are under artifacts/coverage and you have Cobertura format, you can use glob patterns to work around the randomly named directories VSTest creates and merge them like this:

dotnet-coverage merge artifacts/coverage/**/coverage.cobertura.xml -f cobertura -o artifacts/coverage/coverage.xml

It might be interesting to update the docs accordingly - this is far easier than the current suggestion.

@github-actions github-actions bot added the untriaged To be investigated label May 17, 2024
@Bertk Bertk self-assigned this Jul 23, 2024
@Bertk Bertk added documentation and removed untriaged To be investigated labels Jul 23, 2024
@Bertk Bertk added the Solved The issue is solved and can be closed label Jul 24, 2024
@Bertk Bertk closed this as completed Sep 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Solved The issue is solved and can be closed
Projects
None yet
Development

No branches or pull requests

2 participants