Skip to main content
7 events
when toggle format what by license comment
Oct 21, 2013 at 19:37 history migrated from stackoverflow.com (revisions)
Oct 3, 2013 at 15:21 comment added Gigi How about Uncle Bob? butunclebob.com/ArticleS.UncleBob.TheThreeRulesOfTdd The three rules are specific about unit tests.
Oct 2, 2013 at 21:30 comment added Fresh @Gigi "the purist approach is that TDD is unit tests only" - which purist stated this? As Nathan Hughes says TDD can be used equally well at an interaction or a unit level, where the integration tests will drive the creation of unit tests to satisfy the integration test.
Oct 2, 2013 at 18:16 comment added Gigi I understand, and your point is perfectly valid. However, the purist approach is that TDD is unit tests only. It is with the purist approach that I am taking issue. Nonetheless, your input is useful and I'd like to invite you to post an answer to my other question on this exact topic: stackoverflow.com/questions/19142855/… .
Oct 2, 2013 at 18:10 comment added Nathan Hughes @Gigi: I was addressing your assumption that TDD can only test at the method level, I don't think that's necessarily true. Unit tests can test internal consistency of the application code, they only stop short of verifying interaction with external systems. That's what I was trying to get across by distinguishing between unit- and integration-tests. If unit tests were necessarily method-scope then I would agree their helpfulness would be extremely limited.
Oct 2, 2013 at 18:05 comment added Gigi That's not what I'm asking (actually I asked that in another question). My point is: does TDD really result in better design beyond the unit level? How is that possible, given that TDD advocates unit tests (although, as you say, it is entirely possible to do integration tests as well)?
Oct 2, 2013 at 17:49 history answered Nathan Hughes CC BY-SA 3.0