On Mon, 2009-03-23 at 14:20 +0100, Wichert Akkerman wrote:
On 3/23/09 12:57 PM, Chris Withers wrote:
Christian Theune wrote:
Wichert. Be aware of nose issue #102:
http://code.google.com/p/python-nose/issues/detail?id=102 Is there a particular reason to keep using the test_suite convention? Personally I much prefer nose's habit of automatically picking up tests.
I think there is not. One of the reasons I refactored the test runner a while ago was to make it possible to support a less-boilerplate-heavy scheme of getting tests set up.
Well okay, but without test_suite, how do you quickly and easilly disable a class full of tests while you work on something else that will break them but that you don't want to deal with just yet?
nose has a --exclude option
I usually just run the tests that I'm interested (-s or -t or a combination) in during those times. I never had to go in and comment out a test_suite function. -- Christian Theune · ct@gocept.com gocept gmbh & co. kg · forsterstraße 29 · 06112 halle (saale) · germany http://gocept.com · tel +49 345 1229889 7 · fax +49 345 1229889 1 Zope and Plone consulting and development