>That would mean that 80% of your code is completely untested That is not always a bad thing. Maybe depending on the application this 80% is trivial and never

>That would mean that 80% of your code is completely untested That is not always a bad thing. Maybe depending on the application this 80% is trivial and never breaks. It is explained in anti-pattern 4 that you should start with the critical code first. >Most organizations I've worked with recommend at least 80% statement coverage, as a rule of thumb This number is making MANY assumptions. I would demand different code coverage from an application that runs on a nuclear reactor and from an application that is used as point of sale in a small pizza restaurant.