To address controls of MDI applications, TestArchitect
maps the controls as MDI-child windows.
Addressing controls of MDI applications by using the JIT mode
is just fully supported on Microsoft UI Automation
To map a control as a MDI-child window, do
Open the AUT and navigate to the MDI-child window of interest.
Note: The MDI-child window is recognized as a normal control in the Interface
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
Capture UI controls belonging to the newly-captured child window as you
For example, capture a button and a list view controls.
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
might cause the mistake when identifying
UI control, since the nature of employed breadth-first search algorithm.
Save the interface definition.
A new interface entity setting
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.