3 ms·
He goes out of his way to avoid being anti-unit testing on here, but the whole thing does come off as looking as if it's anti-unit testing. I suspect there are
by commandlinefan 6y ago
He goes out of his way to avoid being anti-unit testing on here, but the whole thing does come off as looking as if it's anti-unit testing. I suspect there are just as many anti-unit test posts as there are pro-unit tests, and it really bothers me that these are so common. I can only assume that anti-unit test types, like anti-OO types, were burned by a wacky unit test implementation (and there are plenty!) once and blamed it on the concept of unit tests.
In my experience, as long as each non-trivial function can be invoked on its own through a unit test (that is, without actually spinning up a live database or having remote services available), you're "good enough" on unit tests, and you can manually test the edge cases from there.
- UncleMeat 6y agoEspecially since a lot of the arguments are very personal rather than general. He claims that testing will degrade the sort of flow state that devs want to achieve. But that sounds like something that just affects him personally. Testing can help that state for some people.