Web Add-in Extensibility Developer Guide > Working with Web Add-in Extensibility > Developing Support for Your Toolkit > About Custom Toolkit Support

About Custom Toolkit Support

You implement Web Add-in Extensibility by creating a toolkit support set for each Web toolkit you want to support. The toolkit support set is comprised of XML configuration files and JavaScript functions. The XML configuration files define the test object classes that you create to support the custom Web controls and map them to the controls. In addition, they define how UFT operates on the custom controls. The JavaScript functions provide an interface between UFT and the application being tested, retrieving information about the control and performing operations on it. See also Developing Browser-Independent Support.

This section describes the different files, definitions, and functions that you must include in a custom support set. For more information, see the Toolkit Configuration Schema Help, the API Reference, the JavaScript Function Reference, and the UFT Test Object Schema Help.

Extensibility Accelerator provides sample projects containing toolkit support sets that extend UFT's support for some public Web 2.0 toolkits. These are the support sets for ASPAjax, GWT, YahooUI, and Dojo, which are installed on UFT when you install the Web 2.0 Toolkit Support for Unified Functional Testing. The samples also include Help files for the test object models that UFT uses to support testing controls from these toolkits.

The sample projects are installed under %ALLUSERSPROFILE%\Documents\ExtAccTool\Samples. You can open the projects in Extensibility Accelerator and browse through the toolkit support set files to see examples of how Web Add-in Extensibility can be implemented. Some of the examples in this section are taken from these files.

Note: Before you actually begin to create a toolkit support set, you must plan it carefully. For more information, see Planning UFT Support for Your Toolkit.