background image
<< Chapter 4 About Verification Points | Types of Verification Points >>
<< Chapter 4 About Verification Points | Types of Verification Points >>
Verification Points and Scripts
Creating Verification Points in GUI Scripts
When you play back the script against a new build, Rational Robot retrieves the
information in the baseline file for each verification point and compares it to the
state of the object in the new build. If the captured object does not match the
baseline, Robot creates an actual data file. The information in this file shows the
actual state of the object in the build.
After playback, the results of each verification point appear in the TestManager log.
If a verification point fails (the baseline and actual data do not match), you can select
the verification point in the log and click View >
Verification Point to open the
appropriate Comparator. The Comparator displays the baseline and actual files so
that you can compare them.
Verification Points and Scripts
A verification point is stored in the project and is always associated with a script.
When you create a verification point, its name appears in the Asset (left) pane of the
Script window. The verification point script command, which always begins with
, appears in the Script (right) pane.
Because verification points are assets of a script, if you delete a script, Robot also
deletes all of its associated verification points.
You can easily copy verification points to other scripts if you want to reuse them.
For information, see Copying a Verification Point on page 4-25.
NOTE: The following verification points are not stored in the project and do not
appear in the Asset pane: File Comparison, File Existence, Module Existence,
Window Existence, and Alphanumeric (if the verification method is Numeric
Equivalence or Numeric Range).
List of verification
points associated
with the script
Verification point
commands in the
NOTE: You cannot play back a verification point that you have copied or typed
into a .sbl library source file. The verification point must be in a script or a .rec
library source file. For information about types of library files, see Library Source
on page 3-14.