background image
<< Test Frame - Why change the tags | Test Frame - Mapping and recording Manager Class OSF/Motif widgets >>
Test Frame - Mapping custom classes to standard classes
<< Test Frame - Why change the tags | Test Frame - Mapping and recording Manager Class OSF/Motif widgets >>
User's Guide
95
4 R
ECORDING
A
T
EST
F
RAME
Mapping custom classes to standard classes
Modifying after
pasting
If you need to modify the identifier or tag for the application's main window
or menus, you do so after you have pasted the declarations to the test frame
file, by editing the file directly.
Mapping custom classes to standard classes
While using the Record Window Declarations dialog, you will on occasion
notice that the recorded class is CustomWin, indicating that SilkTest does not
recognize the class of the object. The object is interpreted as a custom object.
If the object is in fact a custom object, then you need to follow the procedures
outlined in Chapter 17, "Supporting Custom Objects", to be able to record
and run testcases that interact with the custom object.
However, if the object is not actually a custom object, but is instead a
standard object that your application's developers have renamed, you will be
able to record and run testcases merely by establishing a class mapping
between the renamed class and the standard 4Test class.
Procedure To perform a class mapping when a declaration for a CustomWin
appears in the Record Window Declarations dialog:
1
Press Ctrl+Alt.
The declarations are frozen in the Window Declaration list box in the
lower half of the Record Window Declarations dialog.