UFT One and the UI Automation framework
UFT One uses the UIAutomation framework elements to:
Create UI Automation test objects based on the objects in your application
Create supported methods for these test objects based on the patterns supported for each object/control type
Create the test object hierarchy based on the UI Automation element tree
For a control that uses the UI Automation framework, the Control Type property describes the basic appearance and functionality of the control in the application.
UFT One translates the Control Type property of an element/object in the application's user interface into a corresponding test object in UFT One:
|If the Control Type property is...||UFT One creates this test object:|
This object must also have implemented the Grid pattern to be recognized as a table.
If the controls in your application use a different value for the Control Type property, or do not have a Control Type property implemented, they are identified as a UIAObject.
For a full listing of all the available values for the Control Type property, see the Control Type Identifers page on MSDN.
UFT One creates test object methods based on a control type's supported patterns. These patterns define a particular aspect of a control's functionality or feature. For a full explanation of how these patterns are used in your applications, see https://msdn.microsoft.com/en-us/library/ms752362(v=vs.110).aspx.
Each test object also supports all UFT One common methods and properties, as well as additional UI Automation-specific methods, including .Click, .SetFocus and .Type. A number of test objects also have object-specific test object methods available for use.
For full details on these test object methods, see the UI Automation section of the UFT One Object Model Reference for GUI Testing.
Note: The test objects and methods available are completely dependent on the properties and patterns implemented in your application. We recommend that you familiarize yourself with the properties of your application's objects - specifically the Control Type IDs and supported patterns to understand what test objects and methods you can use.
UFT One creates test object methods based on the patterns:
|If a object has this pattern...||UFT One has these test object methods:|