Renaming UI Objects
Developing and Working with the Application Map
Generic UI objects represent controls that the Application Mapper encounters
but cannot recognize. Although the Application Mapper queries the control for
recognition properties such as class name, style, and text, it cannot match these
properties with those of a known class in the UI library. Generic objects are
often custom controls.
Action objects represent the actions to which controls in the AUT respond
during mapping. Action objects include LeftClick, RightClick,
LeftDoubleClick, SelectTab, SetState, and ClearState.
An application map contains a single StartAUT action object that represents the
action to start the AUT executable file. The StartAUT object is always the top-
level action object in the application map hierarchy. The Application Mapper
and Pilots use it to start the AUT.
Transition objects indicate where a window closed, where the AUT
terminated, or where the AUT crashed.
Crash transition objects show where the AUT failed during mapping.
Close transition objects show where an action caused a window to close.
Exit transition objects show where an action caused the AUT to terminate
Shortcut objects show where the Application Mapper encountered a window
that was already mapped on a different path through the user interface. The
shortcut points to the window object originally mapped. To display the
properties of the window a shortcut points to, click the shortcut. To jump to the
mapped window object that a shortcut points to, double-click the shortcut.
Renaming UI Objects in the Application Map
As TestFactory maps input controls such as text boxes and combo boxes in the AUT,
it assigns general names such as "TextBox1" and "TextBox2" to the UI objects it
maps for them. To make an input UI object in the application map easier to identify,
you can rename it.
To rename an object in the application map:
1. Click the object.
, and then type a new name in the active text box.