User Guide Interface definitions Addressing windows, controls of Multiple Document Interface applications

 Mapping controls as MDI-child windows

Mapping controls as MDI-child windows

To address controls of MDI applications, TestArchitect maps the controls as MDI-child windows.

To map a control as a MDI-child window, do the following:

1. Open the AUT and navigate to the MDI-child window of interest.

   Notes: 
   The MDI-child window is recognized as a normal control in the Interface Viewer.

2. In the Interface Viewer, from the UI Explorer panel, right-click the control that you’d like to capture as a child window, and then select Set Child Window.

   The control is now captured as a child window. You can verify it from the Settings tab, at the Child window field.
   
   

3. Capture UI controls belonging to the newly-captured child window as you wish.

   For example, capture a button and a list view controls.

   Warning: 
   While selecting TA properties to capture a control as a MDI-child window, it is highly recommended that you do not use the global pos TA property. The use of global pos might cause the mistake when identifying UI control, since the nature of employed breadth-first search algorithm. (Learn more.)
   
   

4. Save the interface definition.

A new interface entity setting action named child window with the value of specified child window is added to the interface entity you are working on.

In this example, frm_chart_check is a MDI-child window, and btn_ok and listview are child controls which belong to the MDI-child window.