<div>
            <div><span>Yep, that's the solution I need. Thanks to all who replied!<br>
                </span>
                <span><br>--&nbsp;<br>Chris Rose<br>Not to be taken literally, internally, or seriously.<br></span>
                
                <p style="color: #a0a0a0;">On Tuesday, February 22, 2011 at 4:33 AM, meme dough wrote:</p>
                <blockquote type="cite" style="border-left-style:solid;border-width:1px;margin-left:0px;padding-left:10px;">
                    <span><div><div>Hi,<br><br>Guess people already worked this out, but pytest-cov supports writing<br>the coverage xml report from all hosts / cores / subprocesses which<br>can then be directly put into hudson / jenkins cobertura plugin.<br><br>:)<br><br>On 17 February 2011 05:41, Ned Batchelder &lt;<a href="mailto:ned@nedbatchelder.com">ned@nedbatchelder.com</a>&gt; wrote:<br><blockquote type="cite"><div>Keep in mind that once you run coverage with the py.test plugin, there is a<br>.coverage data file left behind.&nbsp; That file can then be used to generate<br>reports directly from coverage, outside of any test runner.&nbsp; So once you've<br>run your tests, use "coverage xml" to create an XML file from the .coverage<br>data file.<br><br>--Ned.<br><br>On 2/16/2011 12:14 PM, Chris Rose wrote:<br><br>I'd like to try out py.test; I've found that it's nicer output-wise than<br>nose in a lot of respects. However, we have a significant in-house<br>investment in Hudson/Jenkins automated testing that currently depends on<br>nose + xcoverage + xunit output to tie into the Hudson xUnit/Cobertura<br>plugin support for tracking test coverage and successes.<br>Is there a clear process for tying these things together? I see the<br>--junitxml output flag, so that's part of the issue solved, but it doesn't<br>handle coverage.<br><br>--<br>Chris<br>Not to be taken literally, internally, or seriously.<br><br>_______________________________________________<br>testing-in-python mailing list<br><a href="mailto:testing-in-python@lists.idyll.org">testing-in-python@lists.idyll.org</a><br><a href="http://lists.idyll.org/listinfo/testing-in-python">http://lists.idyll.org/listinfo/testing-in-python</a><br><br>_______________________________________________<br>testing-in-python mailing list<br><a href="mailto:testing-in-python@lists.idyll.org">testing-in-python@lists.idyll.org</a><br><a href="http://lists.idyll.org/listinfo/testing-in-python">http://lists.idyll.org/listinfo/testing-in-python</a><br></div></blockquote></div></div></span>
                
                
                
                
                </blockquote>
                
                <div>
                    <br>
                </div>
            </div>
        </div>