background image
<< Viewing the AUT's identifiers | SilkTest Options/Runtime >>

Close the Record Window Identfiers dialog

<< Viewing the AUT's identifiers | SilkTest Options/Runtime >>
Getting Started: A Tutorial
49
2 P
REPARING
TO
U
SE
THIS
T
UTORIAL
Becoming Familiar with the Client/Server Application Under Test
On the Customer Information window, click Search.
·
Point to the text Customer Number. Notice that SilkTest identifies
it as:
CustomerSearch.CustomerNumberText
.
·
Point to the Customer Number text field. Notice that SilkTest
identifies it as:
CustomerSearch.CustomerNumber
.
·
Point to the Cancel button. Notice that SilkTest identifies it as:
CustomerSearch.Cancel
.
3
Close the Record Window Identfiers dialog.
When you have finished exploring, click Close on the Record Window
Identifiers dialog.
4
In GMO, close the Customer Search Dialog
Click Close.
Dynamic instantiation
Typically before you begin recording your scripts you record a test frame for
your application that contains declarations of each of the windows that you
want to test. But if you have not declared the windows in your application,
SilkTest dynamically instantiates the objects when you record them. This
means that SilkTest automatically creates the unique name based on the
object's class and tag. For more information about classes and tags see
"Basic
object-oriented concepts" on page 8
.
If we were not using the gmoc.inc test frame to view the GMO application.
the SilkTest would have dynamically instantiated the objects as displayed in
the following image.
MainWin("Green Mountain
Outpost|$C:\Green\green.exe"
).ChildWin("Customer
Information").DialogBox("#1|
$59648").CustomWin("[BitMap]
#2|$65535[2]")
MainWin("Green Mountain
Outpost|$C:\Green\green.exe"
).ChildWin("Customer
Information").DialogBox("#1|
$59648").TextField("Customer
Number:|$1000")