About Purify and Robot
Playing Back GUI Scripts
After playback, Robot can integrate the diagnostic tool's results into the Robot log,
so that you can view all of the playback results in one place. You can choose to show
any combination of errors, warnings, and informational messages. Then
double-click a result in the log to open the script in Robot and the appropriate file in
the diagnostic tool.
About Purify and Robot
Robot with playback under Purify works with Visual C/C++ applications on
Windows NT 4.0 and Windows 2000.
Purify detects and diagnoses memory access errors and memory leaks. Without
Purify, the visible symptoms (crashes, malfunctions, or incorrect results) of these
kinds of errors often do not show up until long after the erroneous code was
executed, and in a short test, often not at all. Purify detects and pinpoints the cause
of the error as the code is executed.
Where applicable, Purify adds significant value to Robot, because it finds many
otherwise hidden defects in the application code.
About Quantify and Robot
Robot with playback under Quantify works with Visual C/C++, Visual Basic, and
Java applications on Windows NT 4.0 and Windows 2000.
Quantify profiles the time spent in each module, function, line, and block of code,
and detects performance bottlenecks within an application. Once bottlenecks are
identified, you can focus on the inefficient parts of the code and substitute
alternative implementations or algorithms to improve performance.
By using a Robot script to drive the application, in conjunction with Quantify, you
ensure that a repeatable test is measured for each iteration of performance
improvement. This minimizes the risk of comparing different things when
contrasting a run before and after a possible performance-enhancing code-change.
About PureCoverage and Robot
Robot with playback under PureCoverage works with Visual C/C++, Visual Basic,
and Java applications on Windows NT 4.0 and Windows 2000.
NOTE: During Robot playback under Purify, Quantify, or PureCoverage
(PQC), the PQC data file is not produced until the application-under-test
terminates. Because it takes a few seconds for the PQC data file to become
available after the application-under-test is terminated, PQC information
messages may not be available immediately in the test log in the PQC datafiles
(.pfy, .cfy. or .qfy).