[py-dev] Convention for TDD

Max Ischenko ischenko at gmail.com
Tue Oct 11 07:54:01 CEST 2005


Ian,

> > >>Is there any convention people are using with py.test for
> > >>test-drive-development tests that still fail?  Like a convention for
> > >>saying I-fail-but-don't-worry; some combination of keywords and
> > >>disabling variables so it can only be run explicitly?
...
> > I'm writing some experimental code, and I want to check it in before it
> > is finished.  But I want other people to know that it's okay that the
> > tests fail (while I also want them to be able to see the code's progress).
> 
> there is no single convention i know off.  I guess that
> 
>     DONT_TEST_test_whatever
> 
> is the one i have seen most often.

Certainly a kludge, but you can set class-level attribute "disabled" to exclude whole test class from running. 

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 205 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20051011/be36333f/attachment.pgp>


More information about the Pytest-dev mailing list