[TIP] including (or not) tests within your package

Barry Warsaw barry at python.org
Tue Jul 27 07:04:56 PDT 2010

On Jul 27, 2010, at 03:37 PM, Marius Gedminas wrote:

>On Tue, Jul 27, 2010 at 01:32:20PM +1000, Ben Finney wrote:
>> The trick then becomes management of the build script so that the
>> install step does *not* deploy the tests. Which requires thinking of
>> one's package as a package to be deployed, even though you're
>> deploying it in source form. From that point, it's a matter of
>> learning about Distutils and all the rest.
>Other than wasting a bit of disk space, what are the downsides of
>installing the tests?

To me, nothing.  In fact I think there's a lot of upside to including the
tests.  It helps instill confidence in the installed version of the package,
and it can provide a level of documentation.  I also have in mind a
Python-wide test infrastructure that would install as many packages as
possible, run the tests, and gather health metrics for each package, possibly
indicating the status on the Cheeseshop.

+1 for including the tests by default.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: not available
URL: <http://lists.idyll.org/pipermail/testing-in-python/attachments/20100727/ba302cd3/attachment.pgp>

More information about the testing-in-python mailing list