[py-dev] Convention for TDD

[holger krekel]

On Mon, Oct 10, 2005 at 10:52 -0500, Ian Bicking wrote:
> David Stanek wrote:
> >On Sun, Oct 09, 2005 at 10:13:07PM -0500, Ian Bicking wrote:
> >
> >>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?
> >
> >
> >What exactly are you trying to do? When I practice TDD I like when
> >the tests fail so I know what I need to be working on. Once I get
> >all of the tests to pass I add a couple more knowing that the code
> >to support them is not there and the test will fail.
> 
> 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.  

    holger