Walkthrough - Analyzing Purify Coverage Data to Find Untested Code

Related Topics

If you collected coverage data for the run, you can find the parts of your native-compiled Visual C/C++ code that you haven't Purify'd, and improve your testing coverage so that you find all the errors, wherever they occur.

1.    After a run has completed, use the coverage tabs in the Data Browser window to view the number of functions and lines hit and missed by your tests, as well as the percentage of functions and lines hit and missed.

2.    Create filters to hide data that you are not interested in seeing. Purify automatically filters out non-critical data from system libraries and other modules before displaying coverage details.

3.    If debug line data is available and you monitored your code at line level, use the Annotated Source window to analyze coverage for functions line by line.

4.    Use the Merge Runs dialog box to merge specific runs and view the cumulative effect of selected runs. By default, Purify automatically creates an Auto Merge entry in the Navigator, so you can analyze the total coverage of the program over multiple runs.

If you find weak spots in your coverage, rerun your program and test all the important parts, or revise your makefile or test script to do a more thorough job.

(C) Copyright IBM Corporation 1992, 2010.