Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

5
  • 7
    You nailed it in paragraph 2. Commented Aug 5, 2011 at 12:58
  • 5
    "I haven't seen it personally, but I've heard that some places track code coverage and test counts" I've lived in such an environment and indeed no code ever got thrown out because doing so would cause a test to fail. Until I started debugging the actual tests that is, and found a lot of them having such serious flaws they forced code to produce incorrect results in order for the tests to pass. That's when I coined the question: "who is testing the tests" to which so far I've never had a satisfactory answer from the TDD community. Unit tests for unit tests, anyone? Commented Aug 10, 2011 at 7:36
  • 1
    @jwenting - And this anecdote supports Rei's argument rather nicely. I've found the regression protection aspect of TDD to be overblown in practice, even if it's a solid idea in theory. The tests have to be held to be maintained at the same level as production code for it to work, and it's a bit unnatural to treat non-production code this way - I see the same "code rot" with hardware simulators, code generators, etc all the time. Commented Aug 10, 2011 at 12:32
  • "Really simple tests that were intertwined with the class internals" <-- there's your problem right there. Test only to public interfaces. TDD != UT Commented Feb 10, 2012 at 17:47
  • 2
    @StevenA.Lowe - I know that now, but 9 years ago it wasn't so clear :) "TDD is not a testing skill" Commented Feb 10, 2012 at 17:50