As per many software testing experts, code coverage is a good way to identify the untested code. But the percentages aimed do not necessarily contribute to test quality. Such coverage goals encourage poorly designed tests, written with the only intention of meeting system requirements instead of testing the software correctly. We agree that unit testing is important but when aiming at quality its limited. A useful alternative is functional test coverage through test automation, which tracks whether tests execute important values or sequences of values corresponding to software features.
