background image
<< Test Cases - How recorded commands uniquely identify GUI objects | Test Cases - Java classes >>
Test Cases - Recording 4Test components
<< Test Cases - How recorded commands uniquely identify GUI objects | Test Cases - Java classes >>
User's Guide
5 D
Recording 4Test components
The general syntax of this kind of identifier is:
class("tag").class("tag"). ...
Note To create the dynamic tag, the recorder uses the multiple-tag
settings that are stored in the Record Window Declarations dialog. In
the example shown above, the tag for the Text Editor contains its
caption as well as its window ID. For more information, see "About
tags" on page 85
Recording 4Test components
If you want to hand-write some or most of your 4Test code, or if you want to
add individual lines to an existing testcase, you can use the following
recording tools:
Three additional
recording tools
Record/Window Identifiers
Record/Window Locations
For example, when you're working with a script, you might want to leave the
Record Actions dialog open. Any time you want to verify a GUI object, you
can point to the object in your application and verify it.
You can also use the dialog to write a syntactically correct 4Test statement
based on your manual interaction with your application. This eliminates the
need to search through the documentation for the correct method and its
arguments. Once the statement is recorded, the Paste to Editor button inserts
the statement to your script. For reference information on Record/Actions,
see page 491.
Similar to the Actions command, Record/Window Identifiers records the
fully qualified name of the GUI object you're pointing at, which you can then
insert into your script. This eliminates the need to bring up your test frame
file to find the correct identifier for the object. For reference information on
Record/Window Identifiers, see page 502.
It can be useful to know the position of certain objects, for example objects
that are drawn (like tools on a toolbar) or drawing regions (in a CAD/CAM
package, for example). To record the location of an object, use the Record/
Window Locations commands. For reference information on Record/Window
Locations, see page 504.