Category Archives: TDD

Paul Cowen presented an interesting personal observation of using TDD on the ALT.NET mailing list, under the title “TDD + effort != return“.  The implication being that doing TDD requires extra work during development, extra work in training, extra work … Continue reading →

Roy Osherove has suggested a new name for mocks, fakes, stubs or any test double: Isolation.  True, the myriad of test double names can muddy the language, and Meszaros’ suggested name of “test double” still confuses people that don’t get … Continue reading →

Tony Rasa recently talked about design trade-offs when doing TDD: When “doing TDD,” we consciously make design trade-offs to favor testability. … we end up with a lot of single-implementation interfaces because of testability concerns and from weaknesses with our … Continue reading →

Los Techies(.com), its president, Pablo El Burro, and our sponsors are pleased to announce "Pablo’s Days of TDD" (PDoTDD).  PDoTDD is a day-and-a-half event of workshops, discussion, practice, and training around automated unit testing, specifically the practice of Test-Driven Development … Continue reading →

It’s an age-old question: should our team’s goal be 100% coverage?  A valid question, but one I’ve never much cared about in practice.  The idea is that the team, all practicing TDD, should dutifully measure and add unit tests until … Continue reading →

There was a rather healthy public discussion and debate going on via Twitter today between Roy Osherove, Ayende Rahien, Colin Jack, me, and several others. Michael Feathers even dropped in at one point which was cool.  This all started when … Continue reading →