[TIP] Guidelines for where to put tests & how to package them

Michael Foord fuzzyman at voidspace.org.uk
Fri Feb 26 12:00:05 PST 2010

On 26/02/2010 19:52, Olemis Lang wrote:
> [snip...]
>>> so it would be very nice when defining packaging
>>> conventions, layout ... not to enforce the use of that protocol, so
>>> that if another discovery is used then it could still be compatible
>>> with the more abstract good practices. (all this said from my selfish
>>> position, I confess)
>> Yes, but get_suite/test_suite is not supported, so distutils2 still *should*
>> use a unittest supported protocol.
>> Probably Tarek and I need to discuss how
>> the setup.py test command should work for distutils2. It should support
>> non-unittest tests as well (I guess?) so specifying a unittest suite is not
>> necessarily ideal.
> Well, unittest invokes `suite` callable by default
Where does unittest invoke suite callable by default?


> whereas test
> command invokes `test_suite`. So basically it's a duplicate convention
> AFAICS (CMIIW). If some type of reconciliation is going to happen
> that'd be good, but :
>    - I don't what's the most popular style
>    - the fact is that more similar redundant conventions
>      are emerging these days, so ...


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