[TIP] Test Driven Development
grig at gheorghiu.net
Sat Mar 3 08:51:40 PST 2007
--- Michael Foord <fuzzyman at voidspace.org.uk> wrote:
> Hello all,
> I'm very pleased to see this mailing list, thanks to Titus for
> it up.
> I'm interested in how many people on this list are doing test driven
> development ?
> At Resolver we practise TDD, and have both unit tests and functional
I tend to practice what I dubbed TED -- Test Enhanced Development.
Write some code, then write some unit tests for it, then write some
more code, then write some more unit *and* functional tests -- all the
while watching your test coverage numbers. The coverage numbers are not
absolute, but they're a good yardstick for how well you're testing your
application. And with Titus's 'code forensics' features in the figleaf
module, it's pretty easy to see which code is exercised by your tests
and which code is not.
More information about the testing-in-python