Using Web Add-in Extensibility, you can implement full support for all QuickTest features for your controls. You can implement Web Add-in Extensibility support for a set of controls (also referred to as a toolkit or custom toolkit) by developing a toolkit support set.

Implementing Web Add-in Extensibility consists of the following stages:

1. Planning the Toolkit Support Set

- Determine the set of Web controls that comprise your custom toolkit.

- Define the test object model by determining which test objects and operations you want to support based on the controls and business processes supported by your toolkit.

2. Developing the Toolkit Support Set: A Web Add-in Extensibility toolkit support set is comprised of the following files:

- One test object configuration file, which describes the test object model for your toolkit to QuickTest.

- One toolkit configuration file, which describes which test object class represents each control in the toolkit and how QuickTest interacts with each control.

- One or more files containing JavaScripts that QuickTest can call to perform operations on the custom controls.

3. Deploying the Toolkit Support Set: To deploy your toolkit support set and enable QuickTest to support your controls, you need to copy the files you created to specific locations within the QuickTest installation folder.

After you deploy the toolkit support set, when QuickTest opens, it displays your toolkit name as a child node under the Web Add-in node in the Add-in Manager. If you select the check box for your toolkit, QuickTest supports the controls in this toolkit using the toolkit support set that you developed.

4. Enhancing the Toolkit Support Set: After you have created and tested basic Web Add-in Extensibility support for your controls you can enhance your toolkit support set by using some of the more complex options to fine-tune your support.

When you develop a Web Add-in Extensibility toolkit support set, you can start by creating a simple and basic support set and deploying it to QuickTest. This enables QuickTest to recognize your controls correctly and enables QuickTest user to create and run tests on the controls. You can then enhance your support to enable more complex capabilities, such as filtering the child objects learned with a control and more advanced handling of events when recording a test.