<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#ffffff">
Keep in mind that once you run coverage with the py.test plugin,
there is a .coverage data file left behind. That file can then be
used to generate reports directly from coverage, outside of any test
runner. So once you've run your tests, use "coverage xml" to create
an XML file from the .coverage data file.<br>
<br>
--Ned.<br>
<br>
On 2/16/2011 12:14 PM, Chris Rose wrote:
<blockquote cite="mid:0A7C7374E6034BF58E32753C6781E950@offby1.net"
type="cite">
<div>
<div> <span>I'd like to try out py.test; I've found that it's
nicer output-wise than nose in a lot of respects. However,
we have a significant in-house investment in Hudson/Jenkins
automated testing that currently depends on nose + xcoverage
+ xunit output to tie into the Hudson xUnit/Cobertura plugin
support for tracking test coverage and successes.</span></div>
<div><span><br>
</span></div>
<div><span>Is there a clear process for tying these things
together? I see the --junitxml output flag, so that's part
of the issue solved, but it doesn't handle coverage.<br>
</span> <span><br>
-- <br>
Chris<br>
Not to be taken literally, internally, or seriously.<br>
</span> </div>
</div>
<pre wrap="">
<fieldset class="mimeAttachmentHeader"></fieldset>
_______________________________________________
testing-in-python mailing list
<a class="moz-txt-link-abbreviated" href="mailto:testing-in-python@lists.idyll.org">testing-in-python@lists.idyll.org</a>
<a class="moz-txt-link-freetext" href="http://lists.idyll.org/listinfo/testing-in-python">http://lists.idyll.org/listinfo/testing-in-python</a>
</pre>
</blockquote>
</body>
</html>