Reply to thread

Message: [QUOTE="Bart van Ingen Schenau, post: 3854462"] This is actually the first time I heard such a statement from a proponent of TDD. That actually makes me appreciate TDD more, because now I can see where it fits in the entire process. Except for the part that specifics are addressed by writing a unit test, that process matches with my design process (which is definitely not TDD). I tend to write the specifics down as a requirement that I can later transform into both code and a test. Or I can hand it over to someone else to write those. No problem with that. I don't think it is unique to TDD, but more a property of most Agile processes. I think that idea comes from the fact that most advocates of TDD (that I have seen) only talk about writing the tests before the actual code and that the design emerges from the tests. Especially that last part leaves little room for higher-level considerations that you may need in the design. Your explanation makes it clear that, before writing the first testcase, there is already a (rough) design in place. Even for a brand-new project. I don't think that unit test per-se let the design emerge. I think that design emerges by critical thinking about it, and thinking critically about the unit tests you can create is a way of thinking critically about the design. Bart v Ingen Schenau [/QUOTE]