[TIP] Getting combined coverage with Tox

[Randy Syring]

I asked this on the list not too long ago and here is what I found out:

>     Hey Randy,
>
>     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:
>     https://github.com/schlamar/pytest-cov/tree/2.0/example-tox-project
>
>     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.
>
>     Marc
>


*Randy Syring*
Husband | Father | Redeemed Sinner

/"For what does it profit a man to gain the whole world
and forfeit his soul?" (Mark 8:36 ESV)/

On 06/04/2015 12:02 AM, André Caron wrote:
> Hi all,
>
> I've been searching for a recipe for computing combined code coverage 
> while running Tox to against multiple versions of dependencies.
>
> I found an old thread on this list (dates back to Aug 2011) that 
> discusses this, but there is no clear conclusion:
>
> http://lists.idyll.org/pipermail/testing-in-python/2011-August/004310.html
>
> 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:
>
>     [tox]
>     envlist = py34,py27,coverage
>
>     [testenv:py34]
>     deps =
>       nose
>       coverage
>     setenv =
>       COVERAGE_FILE=.coverage.{envname}
>     commands =
>       python setup.py check
>       coverage run -m nose greet
>
>     [testenv:py27]
>     deps =
>       nose
>       coverage
>     setenv =
>       COVERAGE_FILE=.coverage.{envname}
>     commands =
>       python setup.py check
>       coverage run -m nose greet
>
>     [testenv:coverage]
>     deps =
>       coverage
>     commands =
>       coverage combine
>       coverage report --show-missing --fail-under=100
>
>
> 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.
>
> Do you have any suggestions or know of any alternative ways of doing this?
>
> Thanks!
>
> André
>
>
> _______________________________________________
> testing-in-python mailing list
> testing-in-python at lists.idyll.org
> http://lists.idyll.org/listinfo/testing-in-python

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.idyll.org/pipermail/testing-in-python/attachments/20150604/9dd238d9/attachment.htm>