Sustainable Test-Driven Development

I've been posting more on LinkedIn these days.  Short little nuggets about TDD that people really seem to respond to.  It's all out there if you want to read it, just look for my name on LinkedIn. Anyway, I did so many of these that I realized I could make a sort of lightweight handbook out of them, for the the practitioner why just wants to sharpen his or her TDD skills.  So I

Having established the differences between ATDD and UTDD, how are they the same? Why are they both called “TDD” collectively? Tests ensure a detailed and specific, shared understanding of behavior. If properly trained, those who create these tests will subject their knowledge to a rigorous and unforgiving standard; it is hard if not impossible to create a high-quality test about something

I realized recently that this had been written, but never published.  Part 1 was, but never this second part.  Not sure how that happened.  Maybe I needed a test. :) Anyway, here it is.  Part three is still pending. -Scott-  Expanding the thesis Our central thesis thus far has centered on the notion that TDD is not really about testing, it is really about

Both ATDD and UTDD are automatable. The difference has to do with the role of such automation, how critical and valuable it is, and when the organization should put resources into creating it. AUTOMATION ATDD ATDD’s value comes primarily from the deep collaboration it engenders, and the shared understanding that comes from this effort.  The health of the organization in general, and

<!--[if gte mso 9]> <![endif]--><!--[if gte mso 9]> Normal 0 false false false EN-US X-NONE X-NONE <![endif]--><!--[if gte mso 9]>