background image
<< Test Frame - Recording a login window | Test Frame - About classes >>
Test Frame - Window declaration syntax and structure
<< Test Frame - Recording a login window | Test Frame - About classes >>
User's Guide
83
4 R
ECORDING
A
T
EST
F
RAME
Window declaration syntax and structure
The wStartup constant When you record the test frame, a constant called
wStartup is created. By assigning the identifier of the login window to
wStartup and by recording a new invoke method, your tests can start the
application, enter any required information into the login window, then
dismiss the login window. For more information, see "Handling login
windows" on page 297.
Saving the test frame
After you finish recording declarations for each one of your application's
dialogs, save the test frame file.
Procedure To save a test frame, select File/Save when the test frame is the
active window. If it is a new file, it is automatically named frame.inc (if you
already have a frame.inc file, a number is appended to the file name). You can
use File/Save As to select another name.
When saving a file, SilkTest does the following:
Saves a source file, giving it the .inc extension; the source file is an
ASCII text file, which you can edit
Saves an object file, giving it the .ino extension; the object file is a binary
file that is executable, but not readable by you
Example If you name a frame file myframe and save it, you will end up with
two files: the source file myframe.inc, in the location you specify, and the
object file myframe.ino.
About object files Object files are used for test frames and script files.
Object files are described in "Using object files" on page 134.
Window declaration syntax and structure
This section explains the structure and syntax of window declarations, using
some of the declarations for the sample Text Editor application as an
example.
Every window declaration consists of a class, identifier, and one or more tags,
as shown in the following illustration.