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

Michael Foord fuzzyman at voidspace.org.uk
Thu Jul 29 12:34:28 PDT 2010

On 29/07/2010 20:29, Éric Araujo wrote:
> 0.02 €: As a user, I prefer not to have tests and extensive docs per
> default. I like installing an OS and lots of useful packages on very
> small hard drives/partitions. I’m biased, since I use OS packages that
> are already built and tested for my setup.
Right - horses for courses. As a user it frustrates the *heck* out of me 
when a package doesn't include documentation, especially if I install it 
and then try to use it when I no longer have an internet connection. I 
always trust a package a lot more if it comes with tests, even if I 
don't actually run them...


> Regards
> _______________________________________________
> testing-in-python mailing list
> testing-in-python at lists.idyll.org
> http://lists.idyll.org/listinfo/testing-in-python


READ CAREFULLY. By accepting and reading this email you agree, on behalf of your employer, to release me from all obligations and waivers arising from any and all NON-NEGOTIATED agreements, licenses, terms-of-service, shrinkwrap, clickwrap, browsewrap, confidentiality, non-disclosure, non-compete and acceptable use policies (”BOGUS AGREEMENTS”) that I have entered into with your employer, its partners, licensors, agents and assigns, in perpetuity, without prejudice to my ongoing rights and privileges. You further represent that you have the authority to release me from any BOGUS AGREEMENTS on behalf of your employer.

More information about the testing-in-python mailing list