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.
QASource Blog, for executives and engineers, shares QA strategies, methodologies, and new ideas to inform and help effectively deliver quality products, websites and applications.
Our bloggers are the test management experts at QASource. They are executives, QA managers, team leads, and testing practitioners. Their combined experience exceeds 100 years and they know how to optimize QA efforts in a variety of industries, domains, tools, and technologies.
QASource uses cookies to optimize users' experience. Click "Agree and Proceed" button to confirm your consent to the use of cookies. OR, by continuing to use this website, you implicitly accept the use of cookies. Find out more