One of the really neat side effects of unit testing with high coverage is that it means your components must be suitable for more than one client: your actual p

One of the really neat side effects of unit testing with high coverage is that it means your components must be suitable for more than one client: your actual product and the test cases. This means it decouples all the components which leads to check-ins or pull requests that are also self contained and modular. If you push for good test coverage (less than 100% but more than 80% perhaps?) for your unit tests, you'll get less bugs and more modular code and smaller check-ins.