This document discusses the importance and meaning of test coverage in software testing. It defines test coverage as the total number of requirements tested divided by the total requirements in scope. Maintaining high test coverage is important for reducing unknown risks and meeting contractual obligations. Different types of coverage include test, project, release, design, and execution coverage. Tools like requirement traceability matrices can help measure coverage. The document also discusses approaches to test coverage in agile development, risk-based testing, regression testing, and interpreting coverage metrics and defect rates.

1. Significance of Test CoverageSep 2011

2. ContentsMeaning of test coverageBusiness importance for test coverageTypes of test coverageTools for test coverageTest coverage in AgileTest coverage in Risk based testingTest coverage and Regression test decisionsInterpretation of test coverage numbers

3. Meaning of test coverageTotal number of requirements tested against the total number of requirements in scope

4. Business importance of test coverageTest coverage is the direct indicator of the unknown risks

5. Sometimes it is a contractual requirement to show 100% test coverage

6. Effectiveness of other defect metrics depends on test coverage

7. Many times 100% test coverage from SIT is the entry criteria for UAT and for Go-liveTypes of test coverageTest coverageProjectReleaseDesignExecution

8. Tools for test coverageRequirement traceability matrix

9. Test coverage in AgileSprint 2Sprint nSprint 3Sprint 1Reg Test coverage 0%Reg Test coverage 65%RegTest coverage 85%Reg Test coverage 70%Release XReg Test coverage 100%

10. Test coverage in Risk based testingRisk based testing is conscious decision to reduce testing time

11. In this case test coverage cannot be 100%