[patz]

Actually this piece code is to achieve 80% test coverage or even lower. (It's the target of another remote team.)

From the observation, "Everyone knows when you are forced to write tests you code differently" doesn't hold. If you try to make your code testable, TDD is a better approach. (which means you have to write test first.)

But to people who doesn't know how to make code testable, or even worse, take test coverage goal as a burden. They code before they integrate, they integrate before they test. Such stories happen a lot.

Only if people believe in test first and help them know how to write good/maintainable tests first, can test coverage goal make sense.