<div dir="ltr">Hi all,<div><br></div><div>I thought it would be somewhat easier to manage the list of environment names if we could specify them on multiple lines, so I sent in a quick pull request (#163) to add support for this. Please let me know what you think!</div><div><br></div><div>Cheers,</div><div><br></div><div>André</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Jun 4, 2015 at 11:09 PM, André Caron <span dir="ltr"><<a href="mailto:andre.l.caron@gmail.com" target="_blank">andre.l.caron@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi Randy,<div><br></div><div>Thanks for your quick response :-)</div><div><br></div><div>That repo you linked to is essentially using the same technique, though it adds a neat way to clear the coverage before running the tests. As I state previously, this kind of degenerates when you have multiple explicit environments as you need to list each of them in the `envlist` setting.</div><div><br></div><div>Does anybody on this list have any plans for a built-in pre-/post-command Tox setting or some kind of a plug-in interface that could allow me to achieve the same effect without explicitly listing all environments in the `envlist` setting?</div><div><br></div><div>Thanks,</div><div><br></div><div>André</div></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Jun 4, 2015 at 10:08 AM, Randy Syring <span dir="ltr"><<a href="mailto:randy@thesyrings.us" target="_blank">randy@thesyrings.us</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
I asked this on the list not too long ago and here is what I found
out:<br>
<br>
<blockquote type="cite">
<blockquote>
<p>Hey Randy,</p>
<p>in the upcoming pytest-cov 2.0 you can easily create
different data files for each tox environment and
automatically combine them at the end of the tox run. See here
for an example project:<br>
<a href="https://github.com/schlamar/pytest-cov/tree/2.0/example-tox-project" target="_blank">https://github.com/schlamar/pytest-cov/tree/2.0/example-tox-project</a></p>
<p>Unfortunately, there is no release date yet as I'm pretty
busy right now. However, the 2.0 branch should be quite
stable, so you could give it a try.</p>
<p>Marc</p>
</blockquote>
</blockquote>
<br>
<div><br>
<b>Randy Syring</b><br>
<small>Husband | Father | Redeemed Sinner</small><br>
<br>
<i><small>"For what does it profit a man to gain the whole world<br>
and forfeit his soul?" (Mark 8:36 ESV)</small></i>
<br>
<br>
</div><div><div>
<div>On 06/04/2015 12:02 AM, André Caron
wrote:<br>
</div>
</div></div><blockquote type="cite"><div><div>
<div dir="ltr">Hi all,
<div><br>
</div>
<div>I've been searching for a recipe for computing combined
code coverage while running Tox to against multiple versions
of dependencies.</div>
<div><br>
</div>
<div>I found an old thread on this list (dates back to Aug 2011)
that discusses this, but there is no clear conclusion:</div>
<div><br>
</div>
<div> <a href="http://lists.idyll.org/pipermail/testing-in-python/2011-August/004310.html" target="_blank">http://lists.idyll.org/pipermail/testing-in-python/2011-August/004310.html</a></div>
<div><br>
</div>
<div>I've managed to hack something using some hints from there
and some other tips here and there. Here's a stripped-down
version of what I'm using ATM:</div>
<div><br>
</div>
<blockquote style="margin:0px 0px 0px 40px;border:none;padding:0px">
<div>
<div>[tox]</div>
</div>
<div>
<div>envlist = py34,py27,coverage</div>
</div>
<div><br>
</div>
<div>
<div>[testenv:py34]</div>
</div>
<div>
<div>deps =</div>
</div>
<div>
<div> nose</div>
</div>
<div>
<div> coverage</div>
</div>
<div>
<div>setenv =</div>
</div>
<div>
<div> COVERAGE_FILE=.coverage.{envname}</div>
</div>
<div>
<div>commands =</div>
</div>
<div>
<div> python setup.py check</div>
</div>
<div>
<div> coverage run -m nose greet</div>
</div>
<div><br>
</div>
<div>
<div>[testenv:py27]</div>
</div>
<div>
<div>deps =</div>
</div>
<div>
<div> nose</div>
</div>
<div>
<div> coverage</div>
</div>
<div>
<div>setenv =</div>
</div>
<div>
<div> COVERAGE_FILE=.coverage.{envname}</div>
</div>
<div>
<div>commands =</div>
</div>
<div>
<div> python setup.py check</div>
</div>
<div>
<div> coverage run -m nose greet</div>
</div>
<div><br>
</div>
<div>
<div>[testenv:coverage]</div>
</div>
<div>
<div>deps =</div>
</div>
<div>
<div> coverage</div>
</div>
<div>
<div>commands =</div>
</div>
<div>
<div> coverage combine</div>
</div>
<div>
<div> coverage report --show-missing --fail-under=100</div>
</div>
</blockquote>
<div><br>
</div>
<div>Notice that I'm using the "envlist" setting to force the
"coverage" environment to run last. This has the downside
that I must list *all* environments there. Appart from being
tedious to read (CSV on one single line), I get the risk that
someone forgets to add a new environment's name to the list.</div>
<div><br>
</div>
<div>Do you have any suggestions or know of any alternative ways
of doing this?<br>
</div>
<div><br>
</div>
<div>Thanks!</div>
<div><br>
</div>
<div>André</div>
</div>
<br>
<fieldset></fieldset>
<br>
</div></div><pre>_______________________________________________
testing-in-python mailing list
<a href="mailto:testing-in-python@lists.idyll.org" target="_blank">testing-in-python@lists.idyll.org</a>
<a href="http://lists.idyll.org/listinfo/testing-in-python" target="_blank">http://lists.idyll.org/listinfo/testing-in-python</a>
</pre>
</blockquote>
<br>
</div>
</blockquote></div><br></div>
</div></div></blockquote></div><br></div>