[TIP] coverage - conditionally exclude code?
Albert-Jan Roskam
fomcl at yahoo.com
Mon Jun 8 01:18:21 PDT 2015
--------------------------------------------
On Mon, 6/8/15, Marius Gedminas <marius at gedmin.as> wrote:
Subject: Re: [TIP] coverage - conditionally exclude code?
To: testing-in-python at lists.idyll.org
Date: Monday, June 8, 2015, 8:01 AM
On Fri, Jun 05, 2015 at
07:47:39PM +0000, Albert-Jan Roskam wrote:
>
----- Original Message -----
> > From:
Ned Batchelder <ned at nedbatchelder.com>
> > To: testing-in-python at lists.idyll.org
> > Cc:
> > Sent:
Friday, June 5, 2015 7:39 PM
> >
Subject: Re: [TIP] coverage - conditionally exclude code?
...
> > The first thing
to consider is not doing version-specific exclusion at
> > all. Run your tests under all your
scenarios, combine the coverage
> >
results, and produce a coverage report. Doing this, you
don't need to
> > exclude
anything for specific versions.
>
> Aah, I see. Yes, Andre Caron's email
('Getting combined coverage with
>
Tox', earlier today)
>
> already made me realize that using
'combine' was the way to go. I will
> definitely try this. It's going to
be challenging to get the Windows
>
coverage reports from Appveyor to my own Linux machine, I
guess.
You could use
coveralls.io, I guess.
I use Bitbucket, which, afaik, doesn't work with coveralls.io (or travis). I created an extra 'mirror' Github repo,
with the intention to always push to both Bitbucket and Github. Did not finish that though. Too much tinkering.
In hindsight, I should have used Github.
More information about the testing-in-python
mailing list