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

Support for generating multiple output formats from single test run #75

Closed
coderpatros opened this issue May 3, 2018 · 5 comments
Closed
Labels
enhancement General enhancement request

Comments

@coderpatros
Copy link
Contributor

The back story to this is that I use VSTS for builds. There is out of the box functionality for reporting code coverage totals in the build summary when using the cobertura format. However I'd also like to use the tool fdesjardins/coverage-viewer to generate a nice html report and it requires the standard json output.

I'm happy to do some work in this space but before I start I wanted to see what your opinion was on this.

I figure a nice way to access this functionality would be to allow comma separated values for CoverletOutputFormat. So in my case that would look like /p:CoverletOutputFormat=json,cobertura.

Looking at the code it should be pretty straight forward to implement.

@tonerdo tonerdo added the enhancement General enhancement request label May 3, 2018
@tonerdo
Copy link
Collaborator

tonerdo commented May 3, 2018

@patros Thanks for pointing me to that tool, didn't even know it existed. This will be a good addition without breaking backwards compatibility

@coderpatros
Copy link
Contributor Author

@tonerdo you're welcome. I have a pending pull request with fdesjardins to add support for Windows (and a couple of other minor issues), but short of that it's pretty good.

@hunterjm
Copy link
Contributor

hunterjm commented May 4, 2018

I’ve got a local build of coverlet that has ReportGenerator built in pending danielpalme/ReportGenerator#130. If that gets merged as is and the library package gets published, I’d be happy to open a PR.

Willing to open a separate issue as well to not hijack this one.

@tonerdo
Copy link
Collaborator

tonerdo commented May 5, 2018

@patros all merged in!

@tonerdo tonerdo closed this as completed May 5, 2018
@tonerdo
Copy link
Collaborator

tonerdo commented May 17, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement General enhancement request
Projects
None yet
Development

No branches or pull requests

3 participants