2 ms·
100% unit test code coverage is just Uncle Bob BS and it is infeasible for the most part And while it will give some warranties about correctness, it will not
by raverbashing 8y ago
100% unit test code coverage is just Uncle Bob BS and it is infeasible for the most part
And while it will give some warranties about correctness, it will not fundamentally guarantee the application does what is supposed to do.
Integration tests are certainly better
I can only see the headline being a "great wisdom" to people who have accepted Uncle Bob and TDD crap for too long and without questioning it. Because it is obvious.
Why it is obvious? Because that's how things were done most of the time
When you had 640k of RAM and a C compiler writing unit tests was not impossible, but pretty hard. Testing that your app reacted to inputs and acted correctly was doable and easily automatable. And what wasn't automatable would be tested manually.
Now here comes the "holy highnesses" of testing gurus, gaslighting developers and saying that code with no tests (which tests? automated? unit? the definition is purposefully vague) doesn't work or that the only blessed code is the one that is produced through TDD onanism? No thank you