2 ms·
> Same thing with tests. Nobody can say "fuck it, stop writing tests, the customer will never run this code, or this is too fucking obvious, test stuff that mat
by StavrosK 14y ago
> Same thing with tests. Nobody can say "fuck it, stop writing tests, the customer will never run this code, or this is too fucking obvious, test stuff that matters". That is considered irresponsible. Everyone is supposed to worry about not having enough tests.
I don't know about everyone else, but I definitely worry about having too many tests. For every test I write, I have to weigh how useful the test is versus how likely it is that the thing it is testing will change. If its usefulness is overshadowed by the likelihood that it will be a burden later on, it does not get written.
- rdtsc 14y agoYap. It is very easy to write bad tests -- tests that test too much, tests that test the wrong thing, tests that are too fragile (very timing dependent, they break intermittently and suck up resources in tracking down the cause), tests that are not repeatable (someone inserted random input generation and seeded the generator with the time function).
- Evbn 14y agoApply the same thinking to the feature code you write as well.
- StavrosK 14y agoOh, that threshold is even higher.