Web Add-in Extensibility Developer Guide > Working with Web Add-in Extensibility > Developing Support for Your Toolkit > Teaching UFT to Identify the Test Object Class to Use for a Custom Web Control

Teaching UFT to Identify the Test Object Class to Use for a Custom Web Control

After you define the test object classes that you want UFT to use to represent your controls, you need to map each type of control to a specific test object class.

This identification can be performed using JavaScript functions or condition elements that check the control's properties and determine the test object class that should represent it. To improve UFT's performance of learning custom controls and running steps on them, define the identification elements in such a way that JavaScript function calls are avoided as much as possible.

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 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:

For more information on writing JavaScript functions for Web Add-in Extensibility, see Designing JavaScript Functions for Your Toolkit Support Set.

For information on the structure and syntax of the identification elements, see the Toolkit Configuration Schema Help.

After you teach UFT 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.

See also: