<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Tue, May 31, 2016 at 3:18 PM, Dan Stromberg <span dir="ltr"><<a href="mailto:dstromberglists@gmail.com" target="_blank">dstromberglists@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote"><span class="">On Tue, May 31, 2016 at 2:28 PM, Ned Batchelder <span dir="ltr"><<a href="mailto:ned@nedbatchelder.com" target="_blank">ned@nedbatchelder.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
<p>Dan, the XML file uses the Cobertura file format, which used the
word "condition-coverage". The data in the XML report is the same
as in the other reports, just presented differently.</p></div></blockquote></span><div>Please allow me to restate this in my own words, to make sure I've got it (I'm sure I'll be asked):<br><br></div><div>The coverage.xml that coverage.py outputs, uses the wording "condition-coverage" only because it's required of a well-formed cobertura report?<br><br></div></div></div></div></blockquote><div>For what it's worth:<br><br> xmllint --noout --dtdvalid <a href="http://cobertura.sourceforge.net/xml/coverage-03.dtd">http://cobertura.sourceforge.net/xml/coverage-03.dtd</a> coverage.xml<br><br></div><div>...complains about the many "No declaration for attribute missing-branches of element line", but doesn't appear to care about a missing condition-coverage.<br><br></div><div>But there could easily be software out there that still requires the condition-coverage - a DTD isn't a perfect indicator across all tools.<br><br></div><div>Thanks!<br><br></div></div></div></div>