After you define the test object classes that you want UFT One to use to represent your controls, you need to map each type of control to a specific test object class.
You can limit the identification process of custom controls to HTML elements with HTML tags you specify. This can further improve performance, and is more efficient than defining conditions that check the tagName property.
You provide information enabling UFT One to identify which test object class to use for the different controls in the Controls\CommonIdentification element in the toolkit configuration file, or in the Control\Identification element. In these elements you can define the following:
A set of HTML tags per test object class. When UFT One handles each control, it continues the identification process according to the definitions in the Identification element, only for HTML elements with the specified HTML tags.
A set of conditions per test object class. When UFT One handles each control, UFT One checks the control's HTML properties against the conditions you define in each Control element, and locates the first one whose conditions the control meets.
Note: You can define different conditions and HTML tags for UFT One to use when running on different browsers.
Note: If you specify an identification function at the toolkit level (in the Controls\CommonIdentification element), UFT One does not call any identification functions specified at the test object class level (in the Control\Identification element).
For information on the structure and syntax of the identification elements, see the Toolkit Configuration Schema Help.
After you teach UFT One to identify the test object class to use for the custom control, you can test the basic functionality of your toolkit support set. For more information, see Testing the Toolkit Support Set During Development.