I'll take any chance to repost this: https://testing.googleblog.com/2010/07/code-coverage-goal-80-and-no-less.html https://testing.googleblog.com/2010/07/code-

I'll take any chance to repost this: https://testing.googleblog.com/2010/07/code-coverage-goal-80-and-no-less.html https://testing.googleblog.com/2010/07/code-coverage-goal-80... That said, it's very easy to write tests that produce high code coverage, but do not test much that is useful (do they assert the things we truly need to check for?). It's also a pointless exercise to try and cover every single branch (e.g. does every defensive error check need to be asserted on?) It's a delicate balance and I'm sure some people will disagree with this, even.