in reply to Re2: TDD: a test drive and a confession
in thread TDD: a test drive and a confession

I think we're talking about the same thing

I don't think we are :-) I've come from the other direction. In the old days I did a lot of up-front design and documentation work. Now I incrementally produce the design using TDD and constant refactoring. Most of the design is in the tests - I produce few external design documents, and many of the ones I do produce are discarded as soon as the tests they help me with are written.

This methodology allows me to forget the details because I had to write them down to build tests for them. So, I actually have notes that make sense! :-)

Do you need to keep your notes after you have written your tests? If so, what's in the notes that's not in the tests?

(he asks curiously :-)

  • Comment on Re: Re2: TDD: a test drive and a confession

Replies are listed 'Best First'.
Re4: TDD: a test drive and a confession
by dragonchild (Archbishop) on Sep 17, 2003 at 19:17 UTC
    Do you need to keep your notes after you have written your tests? If so, what's in the notes that's not in the tests?

    Actually, my notes tend to be the holistic stuff I was talking about. Things that would fall under the "User Stories" category, but not as formal. So, yes, having that written down helps out a ton.

    ------
    We are the carpenters and bricklayers of the Information Age.

    The idea is a little like C++ templates, except not quite so brain-meltingly complicated. -- TheDamian, Exegesis 6

    Please remember that I'm crufty and crochety. All opinions are purely mine and all code is untested, unless otherwise specified.

[reply]

      Ahh. So notes == requirements. That makes sense ;-)

[reply]

In Section Meditations