<< Running a Pilot to Check for Memory Errors | Running Scripts to Check for Memory Errors >>

Viewing the Results for Memory Errors

Checking for Memory Errors in Visual Basic and C++ Applications (Windows NT)

5-37

e. In the application map, click the Pilot.
f. Restart the Pilot run.

Setting up the AUT before you restart the Pilot run should solve timing problems
during the run.

Viewing the Results of a Pilot Run to Detect Memory Errors
The Best Script

If you run a Pilot to check for memory errors, TestFactory does not calculate code
coverage for the best script. Instead, it optimizes the best script based on UI coverage.
To get a code coverage value for a best script that was generated during memory
checking, clear the Detect memory errors for this session check box on the

General tab, and then run the script from TestFactory.

Defect Scripts

The Defect Found folder for a memory-checking Pilot can include defect scripts that
uncover memory-related defects, as well as defect scripts that uncover other kinds of
defects (AUT crashes, Visual Basic run-time errors, and assertions). To determine
whether a defect script is associated with a memory error or other kind of defect, you
must view its log in the Test Log window of Rational TestManager. For information
about viewing a script log, see Viewing the Log for a Defect Script on page 5-17. For
information about the kinds of memory errors uncovered by defect scripts, see the
topic Using Purify Messages: Message Types in Rational Purify Help.

If you run a Pilot in an area of the AUT that contains an error unrelated to memory,
the Pilot generates a single defect script for that defect, regardless of how many times
the defect turns up during the run. However, if you run a Pilot in an area of the AUT
that contains a memory error, the Pilot generates a new defect script each time the
error shows up during the run. If this happens, the Pilot results include a Defects
Found folder that contains multiple defect scripts for a single memory error.
Although there is no way to completely avoid generating redundant memory defect
scripts, you can reduce the number of these that a Pilot generates.

If a Pilot generates many defect scripts for a single memory error, do the following:
1. To modify the Pilot stop criteria so that a Pilot run generates fewer defect scripts

(for any kind of defect):
a. Click the Pilot in the application map.
b. Click the Stop Criteria tab, and then do one of the following:

Enter a low target value (between 5 and 10) for the Defects found criterion.

Enter a short run time (such as 00:10) in the hh:mm box for the Run for
criterion.