<< Recovery system | How is the test frame used? >>

Identifier of your application

<< Recovery system | How is the test frame used? >>

Getting Started: A Tutorial

4 C

APTURING

OUR

PPLICATION

The Test Frame

Test frames for client/server applications

When you create a test frame for a client/server application the following
information about the application is captured and stored in the declaration for
the main window:

Note SilkTest allows you to define additional or alternative controls
for MessageBoxClass. For example, you may want to add alternative
static text objects or additional push buttons. For more information,
see the online Help.

wMainWindow

This constant holds the identifier of your application's
main window, that is, the window that is displayed
when you created the test frame. The recovery system
uses wMainWindow to restore the application to that
window when a test fails. This is known as Basestate.

sDir

This constant holds the path of the working directory
of the application under test.

sCmdLine

This constant holds the full path and file name of the
executable to start the application under test.

wStartup

This constant holds the identifier of the first window to
open when the application is started; this window may
be a login or security window. By default this constant
is commented out. This constant pertains to the
configuration of the recovery system.

lwLeaveOpen

This constant holds the identifier of one or more
windows, other than the main window, to leave open
after a testcase has completed execution. By default
this constant is commented out. This constant pertains
to the configuration of the recovery system.

MessageBoxClass

This declaration is automatically included when
creating a new test frame for a client/server
application. It provides declarations for controls that
are commonly associated with a message box, such as
static text for the message and the OK, Cancel, Yes
and No push buttons. This declaration is valid for all
the message boxes in your application.