Any code that I haven't executed in test will dump core in production. No matter how innocuous it is, it will cause a problem.
I have learned this lesson after many years of having it repeatedly pounded into my head. :) Over, and over and over.
While 100% coverage is not sufficient, 0% is BAD. Yes, people will try to game the metric, but that's what code reviews are for.
I have also found that shooting for 100% has an additional benefit. It can show what code is truly unreachable. If it is unreachable, I can usually safely remove it. If I can't, I add a comment saying _why_ it can't be removed as well as why it can't be tested.
I have learned this lesson after many years of having it repeatedly pounded into my head. :) Over, and over and over.
While 100% coverage is not sufficient, 0% is BAD. Yes, people will try to game the metric, but that's what code reviews are for.
I have also found that shooting for 100% has an additional benefit. It can show what code is truly unreachable. If it is unreachable, I can usually safely remove it. If I can't, I add a comment saying _why_ it can't be removed as well as why it can't be tested.