3 ms·
If I have TDD set up...I'll add a breaking test...it's a little more verbose, but the fact that everything else passes gives me a nice sanity test when I revisi
by danso 13y ago
If I have TDD set up...I'll add a breaking test...it's a little more verbose, but the fact that everything else passes gives me a nice sanity test when I revisit the code. And of course, unless I totally bunked the test, I can actually keep the test as part of the suite (yes yes, I'm aware that tests themselves become legacy code that demands maintenance and that nothing comes for free)
- gbog 13y agoI call bs on this tests have a cost mantra. They may have value, i.e. be useful, and then it is ok to spent a few minutes fixing them if needed. But if fixing them is costlier than their expected value, then just skip them. I see many reasoning for not writing tests everywhere and very few reasons are acceptable. In some cases in some non mockable languages it is really too hard, this reason is ok. The only other good reason to not write tests is "I don't want to."