-
Notifications
You must be signed in to change notification settings - Fork 787
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
Provide coverage report format Jenkins can consume #17
Comments
Yes, this is the right spot. Let me take a look. For now would you be able to use a post-processing step using the lcov-cobertura tool to get by for a few days? |
@Iristyle I added the cobertura output but don't have a good way to test it. I've made sure that the output is well-formed XML and matches the output of the file generated by the lcov to cobertura python tool. Try it out and see if it works for you.
should create a Available in version |
Wow, that was fast! Thanks a bunch. I will try to get to checking this out later tonight. |
Nice! I was looking to convert lcov to covertura when I saw the commit. Unfortunately Jenkins crashed on simple report. Here is the cobertura report xml I am trying to process using Cobertura plugin. <?xml version="1.0" ?>
<!DOCTYPE coverage SYSTEM "http://cobertura.sourceforge.net/xml/coverage-04.dtd">
<coverage lines-valid="14" lines-covered="11" line-rate="0.7857" branches-valid="2" branches-covered="1" branch-rate="0.5" timestamp="1352925473714" complexity="0" version="0.1">
<sources />
<packages>
<package name="test1" line-rate="0.7857" branch-rate="0.5" >
<classes>
<class name="code.js" filename="C:\Program Files (x86)\Jenkins\jobs\istanbulTest1\workspace\js\coverage\test1\code.js" line-rate="0.7857" branch-rate="0.5" >
<methods>
<method name="foo" hits="1" />
<method name="bar" hits="0" />
</methods>
<lines>
<line number="1" hits="1" branch="false" />
<line number="2" hits="1" branch="false" />
<line number="3" hits="1" branch="false" />
<line number="6" hits="1" branch="false" />
<line number="7" hits="0" branch="false" />
<line number="8" hits="0" branch="false" />
<line number="11" hits="1" branch="false" />
<line number="12" hits="1" branch="false" />
<line number="14" hits="1" branch="false" />
<line number="16" hits="1" branch="true" condition-coverage="50% (1/2)" />
<line number="17" hits="1" branch="false" />
<line number="19" hits="0" branch="false" />
<line number="22" hits="1" branch="false" />
<line number="23" hits="10" branch="false" />
</lines>
</class>
</classes>
</package>
</packages>
</coverage> and here is the Jenkins exception: Hope it can help stabilize istanbul. |
@bahmutov could you run an equivalent test of taking the lcov output, converting it into cobertura format using the python tool? If that works, you could attach the XML generated by that tool and I can see what need to be fixed. Thanks. |
Looks like the |
Hmm, I guess coberture plugin is broken for this. On Nov 14, 2012, at 3:55 PM, Krishnan Anantheswaran notifications@github.com wrote:
|
@bahmutov Yep, that's it - the missing |
Also noticed that the method coverage doesn't work as expected for the cobertura report, since it needs detailed info about the lines and branches within the method and istanbul does not track anything at this level. Line and branch information should be consistent with other reporting formats though. |
Excellent thank, I am impressed with istanbul, it is a great tool On Nov 14, 2012, at 4:22 PM, Krishnan Anantheswaran notifications@github.com wrote:
|
@bahmutov thanks! |
I think this is the right spot for the request.
Istanbul was recently integrated into Testacular, and it's pretty fantastic. It would be nice to see a format that Jenkins can natively handle, rather than lcov and/or HTML.
It looks like people tend to favor using the Cobertura plugin... and if they have incoming LCov, they convert.
I found an lcov-tocobertura tool, but it's in Python :( Not sure if there are other / better options here I just haven't come across.
Also see post on SO regarding lcov in Hudson / Jenkins.
/cc @taichi
I opened an issue at Testacular to track this as well.
https://github.com/vojtajina/testacular/issues/164#issuecomment-10298818
Thanks for the consideration!
The text was updated successfully, but these errors were encountered: