<div dir="ltr">Hi,<div><br></div><div>@Ned: My real application has several testenv sections with different dependencies and different testing commands, so it's not as easy to fold into a single generative test environment definitions.</div><div><br></div><div>@Carl: Nice to know that the multi-line support is already possible. It feels kind of weird to have commas on that multi-line list and not on other multi-line lists though.</div><div><br></div><div>To sum it up, it seems like there are currently three techniques to compute combined coverage:</div><div>1) add two coverage test environments and force them to run before and after all other environments;</div><div>2) run coverage in append mode; and</div><div>3) use a meta-automation script (e.g. make).</div><div><br></div><div>I'll stick with #1 since it provides the least confusion and doesn't require a meta-script.</div><div><br></div><div>Thanks for your help,</div><div><br></div><div>André</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Jun 5, 2015 at 1:53 PM, Carl Meyer <span dir="ltr"><<a href="mailto:carl@oddbird.net" target="_blank">carl@oddbird.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi André,<br>
<span class=""><br>
On 06/04/2015 10:15 PM, André Caron wrote:<br>
> I thought it would be somewhat easier to manage the list of environment<br>
> names if we could specify them on multiple lines, so I sent in a quick<br>
> pull request (#163) to add support for this. Please let me know what<br>
> you think!<br>
<br>
</span>Multi-line envlist is already possible (because multi-line settings are<br>
built in to the ConfigParser format), you just aren't allowed to omit<br>
the commas. Here's a typical tox.ini for me which uses a multi-line<br>
envlist:<br>
<a href="https://github.com/carljm/django-transaction-hooks/blob/master/tox.ini" target="_blank">https://github.com/carljm/django-transaction-hooks/blob/master/tox.ini</a><br>
<br>
Regarding the larger question about needing to explicitly specify<br>
envlist, your approach to tox.ini feels backwards from what I usually<br>
use. I see envlist as the required canonical listing of all envs, and<br>
`testenv:...` sections as only needed for special cases. Now that we<br>
have the new environment components support (which you can see used<br>
extensively in the above tox.ini), I rarely have specific `testenv:...`<br>
sections at all, often just the envlist and then the generic `testenv`<br>
section.<br>
<br>
And regarding measuring coverage with tox, I don't bother with separate<br>
coverage files or combining, I just use `coverage run -a ...` as the<br>
test command. The downside of this is that it doesn't automatically<br>
erase before a run or automatically report after a run. I usually handle<br>
this just by scripting tox instead of running it directly; either on CI<br>
or locally via a Makefile.<br>
<br>
HTH,<br>
<br>
Carl<br>
<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" target="_blank">http://lists.idyll.org/listinfo/testing-in-python</a><br>
<br></blockquote></div><br></div>