Re:When TDD Fails
by LeafStorm on Saturday October 01, 2011 @09:47PM
(#3061759)
While testing code is important (and I have tried to do better at writing proper tests for my code), the reason that I have not adopted TDD is because when I write a test and it fails, about half the time it's an actual bug in the code, and half the time it's a bug in the test. I view testing as more akin to going back and checking your work after solving a math problem - not as the definition of what your code is supposed to do, but as a verification that you did it right (and that it continues to work right in the future).
[ Parent
| on HN ]
> when I write a test and it fails, about half the time it's an actual bug in the code, and half the time it's a bug in the test.
Well yeah... You'd expect otherwise?
Do you mean when the test fails that it's some sort of not-bug like you changed your mind about what the method should do since writing the test?