<div dir="ltr"><div>This is how I do it:</div><div><br></div> coverage run -m nose ...<div><br></div><div>André</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, May 27, 2016 at 8:29 AM, Chris Withers <span dir="ltr"><<a href="mailto:chris@simplistix.co.uk" target="_blank">chris@simplistix.co.uk</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On 06/01/2016 18:30, Ned Batchelder wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
FWIW, I strongly prefer using coverage to run nose rather than the other<br>
way around. I guess that's to be expected :) This may be an effect of<br>
the nose coverage plugin somehow.<br>
</blockquote>
<br>
How do you do this?<br>
<br>
my naive:<br>
<br>
coverage run nosetests<br>
<br>
...gives "No file to run: 'noestests"<br>
<br>
Chris<br>
<br>
_______________________________________________<br>
testing-in-python mailing list<br>
<a href="mailto:testing-in-python@lists.idyll.org" target="_blank">testing-in-python@lists.idyll.org</a><br>
<a href="http://lists.idyll.org/listinfo/testing-in-python" rel="noreferrer" target="_blank">http://lists.idyll.org/listinfo/testing-in-python</a><br>
</blockquote></div><br></div>