Custom Objects - Mapping custom classes to standard classes
which is a library of functions that allow for the creation of objects and the
mechanism of interaction with them. In supporting these libraries, SilkTest
contains algorithms to interrogate the objects based upon the standard
libraries. When these algorithms do not work, SilkTest reports the object as a
CustomWin.
looks like a normal text field, but SilkTest calls it an object of the class
CustomWin.
named differently than the standard name. For example, instead of it
being named a TextField, it was named EnterTextRegion. If this is the
only reason, then you can class map the control to the standard name, as
described in the next section, "Mapping custom classes to standard
classes".
work if the object isn't really a custom object, but rather a standard
control with a non-standard name. Try this as your first attempt at
dealing with a CustomWin.
under test that creates and manipulates the object is not from the standard
library. That means that the SilkTest algorithms written to interrogate this
kind of object will not work, and other approaches will have to be used to
manipulate the object.
graphical controls" on page 319. If the object is not a graphical control,
such as a text box, see "Supporting nongraphical controls" on page 322.
CustomWin, but is actually a standard GUI object which the application
developers have renamed, you should map the custom class name to the
built-in class name while in the dialog.