2 ms·
No unit test should be mostly to make sure the old assumptions for code you don't know still hold and warn you if you break something. Ofc if you do the code a
by xwolfi 5y ago
No unit test should be mostly to make sure the old assumptions for code you don't know still hold and warn you if you break something.
Ofc if you do the code and the unit test, all you validate is that the code does what you assumed was right. But in 2 years, when someone touches something unrelated, he'll kiss you on the mouth that your test noticed an edge case that started failing.
If it's not your unit test catching unintended changes, it's your client. You may not want that :)
- meheleventyone 5y agoI'm not arguing against unit tests. Just that using them to speed up iteration is not a good way to approach that problem. They can of course be useful for other things. And obviously the things they don't test will still be found by the client in particular all the things you miss by not actually increasing iteration speed.