3 ms·
I 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 t
by gbog 13y ago
I 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."