Test Coverage

When we start testing there are so many question arises like

How much testing is enough?

When we will say the product is good to go?

How we can assure the quality of the product is good?

When we will have to stop testing?

Is the 100% test coverage is important?

Can we achieve 100% test coverage with in timeline?

When we will say testing is sufficient?

How do we measure the software testing completeness?

See in my point of view we can measure the quality by doing the requirement coverage, defect coverage, code coverage.

When we say requirement coverage that mean how many requirements are get validated? Can all requirements trace the respective test cases? Do all the test cases have passed? In vice versa trace the test cases to the specific requirement that requirement is need to be passed. In short software needs to be tested against the all requirements

In Defect Coverage in need to be known how many defect we found? How many defects has fixed?

Code coverage is all about evaluating the test cases against the actual code. We also do the code coverage by doing statement coverage, decision coverage,

  

 See basically when you execute the test case you are testing the component, feature and requirement too. One test case can cover zero or more component and zero or more requirements.  The term Test Case Coverage means to me a measure of how many of the product requirements are being tested by the defined test cases. It is the testers’ job to define their test cases based on the requirements and the goal should be 100% coverage or close to that.

 Test coverage Formula= (Total no of test case executed/ Total no of test case planned)*100

Test coverage ensure that testing is carried out effectively .