3 ms·

From the conclusion: So for the time being, I'm quite comfortable with my testing approach. I've given up on "pure" TDD of writing one test at at time. I'll ha

From the conclusion: So for the time being, I'm quite comfortable with my testing approach. I've given up on "pure" TDD of writing one test at at time. I'll happily write a block of tests and then the code. I'm also happy to write a block of code and then the tests. I can now even cite a study to show that I'm not a complete moron, even if one study is little more than anecdotal information. The title is somewhat misleading; it's a discussion of test first vs. test last, not testing vs. not testing.

10ren 17y ago
The title isn't "Why I Don't Do Testing", but "Why I Don't Do TDD". Test-driven development is explicitly test-first.
- jon_dahl 17y ago
  Agreed and understood. But for better or for worse, TDD is often used as a synonym for unit testing.
  - olavk 17y ago
    And unit testing is frequently used as a synonym for automated testing (at least thats my experience).