3 ms·
> For example it's paramount to test your software, but whether this is TDD or not is secondary. If you don't examine your motivations for writing tests, and e
by urbanautomaton 15y ago
> For example it's paramount to test your software, but whether this is TDD or not is secondary.
If you don't examine your motivations for writing tests, and evaluate whether they're being fulfilled, how do you know their necessity is paramount?
- shin_lao 15y agoIt's difficult to know if your software works if you don't test it.
- michaelcampbell 15y agoUnless you're Knuth. But I'm not, so I test.
- urbanautomaton 15y agoRight. But that's not the only reason to write tests, and presumably if your tests were giving you false positives, you'd want to note and address that. If "are my tests telling me when my software fails?" is a valid question to ask oneself, surely so is "are my tests telling me when my design is flawed?" Of course, you might not believe that design feedback is an important motivation for writing tests, which is absolutely fine, but then the issue isn't that the OP is "focusing too much on process and methods" - he simply has different processes and methods to you.