Test coverage refers to measuring the degree to which the code or requirements are executed by a test suite. It helps identify areas that are not tested and improve test quality. Measuring test coverage establishes traceability between requirements and test cases, enables change impact analysis, and prevents defect leakage. Test coverage can be achieved through techniques like bi-directional traceability, static reviews, converting defects to test cases, and using code/unit test coverage tools. Maintaining adequate test coverage provides benefits like early defect prevention and better return on investment, while best practices include periodic maintenance, quality gates, using test management tools, and maintaining coverage metrics.

1. Test Coverage By: Phanindra Kishore DBV, QA Manager: AVACorp

2. What is Test Coverage? Finding areas of a requirement not exercised by a set of test cases Creating additional test cases to increase coverage Determining a quantitative measure of Test coverage, which is an indirect measure of quality Identifying redundant test cases that do not increase coverage

3. Why do we need to measure Test Coverage Test Coverage is an important activity which requires high attention to manage the testing activities, then the deliverable will be of high quality. The following can be achieved with Test Coverage: Traceability between the requirements and test cases can be established by measuring the Test Coverage. Change tracking, Impact analysis will be effective if we have proper Test Coverage mechanism in place Defect leakage will be prevented with proper Test coverage Gaps in requirements, test cases and defects at unit level and code level can be found in an easy way

4. How Test Coverage can be achieved? Test Coverage can be achieved in the following ways by using the manual techniques and automated tools: Test Coverage can be achieved using and mandating the bi-directional traceability matrix 2. Test Coverage can be achieved by implementing the static review techniques like inspections, walkthroughs and Peer reviews. 3. More Test coverage will be achieved by converting the ad-hoc defects into executable test cases. 4. Test coverage can be achieved at code or Unit test level using the automated code coverage or Unit test coverage tools. 5. Functional Test Coverage will be achieved by means of proper test management tools which will establish the traceability between requirements, defects and test cases

5. Benefits and Best Practices to adequate Test Coverage Benefits: Defect prevention at early stages of project life cycle. Better ROI will be achieved by reduction in UAT defects and production defects Time, Cost and Scope will be in control Testing life will become smooth by managing the Risk based testing approach Best Practices: Cleanup or maintenance activities need to be performed at frequent intervals of time. Quality gate mechanism should be in place to verify the results Usage of Test management tools will have better control in all aspects of coverage from requirements, test cases and defects. Need to maintain metrics around to measure the Test Coverage percent