PureCoverage uses global filters to remove data for non-critical functions from system libraries and other program modules before it displays the coverage data for the program you're monitoring. PureCoverage's global filters are contained in the filter file Coveragew_exe.cft.
As you analyze the coverage data, you can easily create additional filters for your program by selecting the QuickFilter command from the shortcut menu in the Coverage Browser window or using the Filter Manager dialog box. You can filter data by module, by source file, or by function. When you create and save new filters, PureCoverage saves the filters with the existing filters in the PureCoverage filter file (.cft) <Exename>_exe.cft.
QuickFilter is the fastest way to create and apply a filter. Select one or more modules, source files, or functions to hide and then select the QuickFilter command from the shortcut menu in the Coverage Browser window. PureCoverage assigns filter properties based on your selections and creates a filter for each selected module, source file, or function.
Use the Filter Manager dialog box to create, edit, and maintain filters. To save any changes you make for future runs of the program, click Save Settings in the Filter Manager dialog box. PureCoverage saves the filters in the filter file <Exename>_exe.cft. The filters in this file apply to all runs of the program <Exename>, unless you disable them in the Filter Manager dialog box.
If you create, edit, and apply filters, and then want to use your previously saved filters, click Revert to Saved, and then click Save Settings again to save it for future runs. If you want to use the PureCoverage global filters again, click Reset to Default, and then click Save Settings again to save it for future runs.
You can also create filter files for specific modules, such as DLLs, to use whenever you monitor a program that uses that module. For more information, click
When you run from the command line and save coverage data to an ASCII text file, PureCoverage also provides a command-line option for controlling the use of filters. This is especially useful in test harnesses or scripts. For example, you might add this line to the beginning of a test script:
coverage /SaveTextData /FilterFiles=test_harness.cft hello.exe
This line instructs PureCoverage to monitor the program Hello.exe, then save the output to a text file using the filters contained in the filter file Test_harness.cft.
Notes:
§ The PureCoverage global filters are different depending on whether you are monitoring a Visual C++ program, a Visual Basic program, or Java code.
§ For details about filter file names and their locations, click .
(C) Copyright IBM Corporation 1993, 2010.