2 ms·
You rarely need to implement something that has a full testsuite/proof already. You're typically building something new, which means that if you write tests/pro
by astrange 3y ago
You rarely need to implement something that has a full testsuite/proof already. You're typically building something new, which means that if you write tests/proofs for it, those are also new code which means they might also be wrong.
- eru 3y agoTo give a practical perspective: Automated tests aren't all that useful to make sure that the code you just wrote does the right thing. People can and do use informal manual testing for that, plus careful crafting and review of the code. Where automated tests really shine is in preventing your shiny new PR from accidentally messing up the feature you implemented a month ago. Yes, tests can be wrong. They are still useful for the above, though.