-
Notifications
You must be signed in to change notification settings - Fork 115
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
Cobertura XML test coverage output #87
Comments
Thank you for opening this issue! I was not familiar with
Since the input to the xml is a file created by I found https://github.com/t-yuki/gocover-cobertura which seems to be exactly what would be needed. It appears to read the standard go coverage files and output the Cobertura XML format. If I understand correctly the I'm hesitant to integrate that tool since the code wouldn't benefit from that integration. |
Maybe I am missing something, but Go 1.10 (
ACK
Thanks for having a look! I must have somehow missed this tool when searching for ways to get the coverage reports into our test analysis.
ACK |
It is definitely possible I am wrong. I should elaborate on how I reached this conclusion:
There may be other features of I guess maybe the reports it produces may be a better than what the standard |
Thanks for writing down the history. I only looked at the current page and am not that familiar with the history of the Go ecosystem. From your write up it seems indeed that |
Hi, @dnephin wrote best summary ever, after dealing with those issues for several years I can confirm there is really nothing much to add. To me gocov is obsolete since we can do now Now the only missing thing is test output and coverage output conversion to different formats. This library seems to deal with tests and I'm using https://github.com/t-yuki/gocover-cobertura for coverage. But honestly, for simplification, I really would love to use just one, well maintained, tool. Especially that gocover-cobertura doesn't seem to work really well, there are issues with paths for example. If you guys have ever time or desire to properly handle coverage as well then it would be really amazing. |
We already use gotestsum for JUnit XML output and would also like to output our line-by-line test coverage in Cobertura XML format, because that is what our test analysis system understands.
Currently we have to use 2 additional tools for that (i.e. three tools in total):
go test -coverprofile=...
into a gocov-specific JSON formatIs it possible to integrate the functionality of these tools into gotestsum, so we need less tools and have a one stop shop for test analysis?
The text was updated successfully, but these errors were encountered: