[TIP] How to concisely describe TDD
fuzzyman at voidspace.org.uk
Tue Nov 6 09:00:45 PST 2007
Although TDD is *part* of the design process it isn't the whole story.
Having an iterative development cycle is part of extreme programming and
works with TDD for design. At Resolver we also have 'whiteboard
discussions' where we do our design.
TDD is more for the low level design and API decisions, you still have
to build the higher level design into your whole development process.
My 2c worth.
Michał Kwiatkowski wrote:
> Hello list,
> I'll be giving a lecture on agile on my university this month. I want
> to mention TDD as well, but time constraints make it hard to do. Do
> you have any ideas on how to describe TDD with its red-green-refactor
> cycles in <5 minutes?
> I would like to show some real code as well. I'm considering RSpec and
> doctest, can't decide yet which can be easier to understand. Note that
> the audience may not be familiar with dynamic languages or testing
> whatsoever. I also have a problem in describing TDD as a design
> activity to people accustomed to UML for design and code for
> implementation. Showing them code may give them wrong impression that
> I'm doing implement-with-no-design thing, and I'm precisely trying to
> avoid that. Thanks in advance for any comments.
> testing-in-python mailing list
> testing-in-python at lists.idyll.org
More information about the testing-in-python