Earlier quoted context omitted.
If I recall correctly, even NASA found unit testing to be of limited value, finding a small fraction of software bugs. That's not to say "don't do it" but my stance is that the developer should do some ad-hoc testing for everything they write, just don't formalize and document it or you'll land on the wrong end of cost/benefit. I can point to some subtle logic bugs that no sane unit test would have caught.
"even NASA" implies that NASA is the objective paragon of software development. There are many ways to develop software, and while I have never worked for NASA I can virtually guarantee that their development process is not the same as some random web service. I've found that it's better to think of unit tests as a contract. You don't write them to check your code for bugs, you write them to declare an explicit (thou…
Sure. They have some of the highest costs of failure post-deployment of anyone, and they have some solid development practices. I'll cite NASA in this context any time. Feel free to pull in other sources if you don't like them though.