The following table summarizes each Robot verification point.
Alphanumeric
Captures and tests alphanumeric data in Windows objects
that contain text, such as edit boxes, check boxes, group
boxes, labels, push buttons, radio buttons, toolbars, and
windows (captions).
You can use the verification point to
verify that text has not changed, to catch spelling errors,
and to ensure that numeric values are accurate.
Clipboard
Captures and compares alphanumeric data that has been
copied to the Clipboard. To use this verification point, the
application must supply a Copy or Cut capability so that
you can place the data on the Clipboard. This verification
point is useful for capturing data from spreadsheet and
word processing applications as well as terminal emulators.
File Comparison
Compares two specified files during playback. The
comparison is based on the contents of the files and their
sizes, not on the file names or dates. When you create the
verification point, you specify the drive, directory, and file
names. During playback, Robot compares the files
byte-for-byte.
File Existence
Verifies the existence of a specified file during playback.
When you create the verification point, you specify the
drive, directory, and file name for the required file. During
playback, Robot checks to see if the file exists in the
specified location.
Menu
Captures and compares the menu title, menu items,
shortcut keys, and the state of selected menus. Robot
records information about the top menu and up to five
levels of sub-menus. Robot treats menu items as objects
within a menu and tests their content, state, and accelerator
keys regardless of the menu item's location. (You can also
use the Object Data verification point to test a menu.)
Module Existence
Verifies whether a specified module is loaded into a
specified context (process), or is loaded anywhere in
memory. Each process has its own context, which includes
a set of loaded modules. When you create this verification
point, you select the name of the module. You can also
select the name of a context (process), in which case the
verification point tests whether the module is loaded into
that process. If no context is specified, the verification
point tests whether the module is loaded anywhere in
memory.
