So, excluding life-critical software, it's still a business decision. Engineering will naturally tend to geek out on infrastructure projects like this and they

So, excluding life-critical software, it's still a business decision. Engineering will naturally tend to geek out on infrastructure projects like this and they need to be kept focused on the business case. There has to be some push-back. What is the cost of even one engineer working full-time on build verification? The thing you really want to avoid is getting blind-sided by devastating bugs or systemic process problems. So it's a balance. I've just seen many cases where projects got bogged down as developers built their super-uber-build-test framework. It's easy for people to push these projects through without rationally investigating the cost / benefit, because ... because ... you're not seriously suggesting that we shouldn't test more, you monster!?