background image
<< Close the Record Window Identfiers dialog | What You Have Learned >>

SilkTest Options/Runtime

<< Close the Record Window Identfiers dialog | What You Have Learned >>
50
Getting Started: A Tutorial
2 P
REPARING
TO
U
SE
THIS
T
UTORIAL
Becoming Familiar with the Client/Server Application Under Test
Note If you would like to try this yourself, you must remove the
gmoc.inc file from the SilkTest Options/Runtime Use Files.
SilkTest uses the following syntax when tagging dynamically instantiated
objects in client/server application:
Syntax:
class("tag ")
Example:
MainWin("Green Mountain
Outpost").ChildWin("Customer Information")
In this declaration:
·
MainWin
refers to the class of the application's main window.
·
Green Mountain Outpost
is the identifier, Caption in this example, of
the object, MainWin.
·
ChildWin
is the class of the Customer Information Window.
·
Customer Information
is the identifier of the ChildWin.
For more information about dynamic instantiation or syntax and structure,
see the online Help.
Multi-tagging
SilkTest also provides additional information for dynamically instantiated
tags, when available. For example:
Syntax:
class("caption|index|window ID ")
Example:
PushButton("Add|$1010")
In this declaration:
·
PushButton
is the class of the object
·
Add
is the caption.
·
$1010
is the window identifier.
By multi-tagging, or generating any of the five types of tags: caption, prior
text, index, window identifier and location for each object, a higher rate of
object recognition is obtained. Since SilkTest identifies an object by the tags,
if one of the tags does not match, but the others do, your testcase will still
succeed. For example, if you record a caption and window ID for an object
and the caption changes (such as from "Open" to "OK") but the index
remains the same, SilkTest is still able to find the object based on its window
ID. For more information about multi-tagging, see the online Help.