Upon startup, the Interface Viewer takes inventory of every open window in the
system on which it is pointed, and displays each one as a node in its UI
During this system intake process, the
Viewer keeps an eye out for an open window to which the active interface entity (if any) is
mapped. (That is, a window whose property-value pairs match those specified by the
interface entity setting action(s) of the interface entity.) If the matching
window is found, its node in the tree is highlighted and partially expanded.
Two views are available for this panel: Class View
Tip: To switch between these views, use the menu, or .
Class View and Hierarchy View of the same interface
Class View groups GUI controls and elements by their TA classes, displaying
the classes as the first tree level beneath the window node, and the actual controls as subnodes
of their respective classes. As such, this view is limited to these two sublevels. Unmapped
control nodes are labelled with the value of a property that the Interface Viewer has chosen as
a suitable identifier. Mapped nodes have this value in parentheses, preceded by the TA name in
Hierarchy View, by contrast, displays the container relationships between
objects (windows, panels, controls, elements, etc.), also in tree form. As such, there is no
restriction on the number of levels that can exist in subtrees in this view. Unmapped nodes
consist of a TA class name in boldface, followed by the value of a property that the Interface
Viewer has chosen as a suitable identifier. Mapped nodes also include the TA name in uppercase.
Desktop mode and Device mode
Desktop mode gives you the access to the GUI environment of AUTs running on
Device mode is pretty self-explanatory. Similar to desktop
mode, device mode gives you the access to the GUI environments of
AUTs running on mobile devices that are currently connected to your host machine.
- To switch between these modes, use the
- Alternatively, if your aim is to enter device mode only, click the
on the Interface Viewer's toolbar.
Icons in the UI Explorer panel
- The term synced (short for synchronized) here means that a) the
given window/control is already mapped to an interface entity/element, and b) the associated
interface entity is currently open in TestArchitect client.
Hence, unsynced does not necessarily mean that no mapping exists for the given
window/control – it could simply be the case that the associated interface entity is not
- For simplicity, menu items and other parts of the Interface Viewer's interface use the term
map, rather than sync.
- By default, TestArchitect organizes all interface elements
by their TA class property. If you want to ungroup them:
- From the Interface Viewer, select the Settings menu.
- Clear the Group Elements check box.