RETIRED CONTENTPlease note that the content on this page is retired. This content is not maintained and may contain information or links that are out of date.
IT must know how thoroughly their source code has been tested. Without this knowledge there will be costly and embarrassing surprises when users run defective parts of the code that IT never executed before release. Code coverage analysis is one of the best ways to measure the amount of source code tested, since it measures how much of the program constructs have been executed. IT can use code coverage to identify parts of the system that they may want to test more rigorously and allow the testers to judge when the source code has been tested enough.
Testing Without Code Coverage Analysis
Where test measurement is done, the most common way to measure testing is to keep a list of scenarios in the form of use cases (based on requirements) that should work with the system, and then test the system with these scenarios. The use cases describe a main scenario, alternate scenarios and error scenarios that are useful for test planning. However, this approach can miss the underlying complexities of code that is being executed.