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

[Michael Foord]

On 25/02/2010 16:18, C. Titus Brown wrote:
> [snip...]
> And, when a setup.py is present (i.e. dev environment),
>
>    % python setup.py test
>
> is going to be the new standard in the brave new distutils2 world.
>
> Does that makes more sense as a backstore? ;)
>
>    
Your example for a setup.py shows the following:

test_suite='somepackage.tests.get_suite'

Is test_suite a setuptools extension to distutils? Is it required to be 
a callable and will distutils2 use the same mechanism? If so then 
unittest(2) ought to have some support for it rather than being 
something that is *only* useable from setup.py.

Why not just:

     tests='somepackage.tests'

Or even default to test discovery?

All the best,

Michael Foord


> thanks,
> --titus
>    


-- 
http://www.ironpythoninaction.com/
http://www.voidspace.org.uk/blog

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.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.idyll.org/pipermail/testing-in-python/attachments/20100226/8161e6a2/attachment.htm>