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

Create cover output to Clover converter #4

Closed
handcraftedbits opened this issue Jul 31, 2015 · 6 comments
Closed

Create cover output to Clover converter #4

handcraftedbits opened this issue Jul 31, 2015 · 6 comments

Comments

@handcraftedbits
Copy link
Collaborator

Create a converter that can take go test -cover output and convert it into Clover format.

@handcraftedbits
Copy link
Collaborator Author

Closing. Go test results don't seem to fit well into the Clover model and supplying a clover.xml file isn't sufficient -- you either need a licensed Clover plugin for Bamboo or a licensed Ant/Maven plugin that generates the HTML. Prefer the approach in #5.

@mheese
Copy link

mheese commented Oct 16, 2015

That is not entirely true. For our Node.JS projects, we use "Istanbul" which can produce the necessary Clover output and report HTML. We also don't have a licensed Clover plugin for Bamboo, and the integration works just fine.

Not sure if that is an option, but just to let you know that there are alternatives available.

@handcraftedbits
Copy link
Collaborator Author

Thanks for the info. Can you show me where you do this? The problem I had was that I could generate a clover.xml no problem but it seemed like the Maven plugin was what turned it into HTML. I had assumed Bamboo would do the conversion but it didn't appear so.

@dhulihan
Copy link

Is there an alternative coverage format that bamboo uses that we can generate a report in? How about NCover?

screen shot 2017-08-15 at 2 56 51 pm

@handcraftedbits
Copy link
Collaborator Author

Ultimately I don't think Clover output fits Go code very well -- it's very much structured in terms of classes and methods. What I think works better is what's in the issue-5 branch (which I haven't messed with in a long time unfortunately) -- merging all the go-generated HTML coverage reports together and then adding them to a custom Bamboo tab. I already wrote code to do the merging, but what's left is:

  1. Reworking the command-line/package handling in the various tasks.
  2. Creating a custom Bamboo tab.

Unfortunately the Bamboo API isn't well-documented (especially when it comes to something like a custom tab -- absolutely no documentation at all) and that's kinda where I left off.

@dhulihan
Copy link

I like the idea of merging coverage reports together and a custom tab. No more transcription to awkward java reporting formats.

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

No branches or pull requests

3 participants