[TIP] coverage - conditionally exclude code?
Marius Gedminas
marius at gedmin.as
Sun Jun 7 23:01:06 PDT 2015
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.
Marius Gedminas
--
Contributing to existing projects is certainly a good method when possible, but
I don't think you'd get very far asking MongoDB developers why they didn't try
to get their changes progressively into PostgreSQL or MariaDB.
-- davidstrauss on LWN
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 173 bytes
Desc: Digital signature
URL: <http://lists.idyll.org/pipermail/testing-in-python/attachments/20150608/4b49f367/attachment.pgp>
More information about the testing-in-python
mailing list