in reply to Unit Tests and Creative Tension

I tried it a couple of times but ended up not doing it very often. Don't know why, maybe because I don't do large enough things so when I discover I'm done with a task it's already too late to start an unfinished failing test :)

As for not being suitable if you're more than one (I rarely am :), I don't see why it wouldn't work if you just keep the failing test for yourself, i.e. don't break anything by checking it in.

Replies are listed 'Best First'.
Re: Re: Unit Tests and Creative Tension
by bunnyman (Hermit) on Sep 10, 2003 at 14:32 UTC

    just keep the failing test for yourself, i.e. don't break anything by checking it in.

    If you are using the Test::More module, you can declare that a test is supposed to fail because it is testing something that is not ready yet. This is called a TODO test.

[reply]

In Section Meditations