I can point to some subtle logic bugs that no sane unit test would have caught.
I can point to some subtle logic bugs that no sane unit test would have caught.
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 (though incomplete) contact that's checked in to source control.
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.
But the constraints, requirements, and priorities for a given project at NASA won't even be the same as every other project there, let alone projects at pretty companies in different fields.
By extension, I would argue that the concept of universally superior development best practices as a whole doesn't make sense.