Eh, not breaking APIs other teams or customers depend on is very very important. I think broad test coverage is justified there. Of course there are always ex

Eh, not breaking APIs other teams or customers depend on is very very important. I think broad test coverage is justified there. Of course there are always exceptions, and testing philosophy should bend to the goals of the organization, not the other way round. And if a five line bash script is a more suitable test than a unit test in the same language as the application, then that's what you should do. Assuming you have a good way to automate it as part of an automated build and deploy process, of course.