Before you begin to create support for a custom toolkit, you must carefully plan the support. Detailed planning of how you want UFT One to recognize the custom controls enables you to correctly build the fundamental elements of the custom toolkit support.
About Planning UFT One Support for Your Toolkit
Extending the UFT One Web Add-in's support to recognize custom controls is a process that requires detailed planning. To assist you with this, the
The first step is determining general information related to your custom toolkit, after which you define the specific information related to each control you want to support.
Preparing to Create Support for a Custom Toolkit
Before you begin planning support for custom Web controls, make sure you have full access to the controls and understand their behavior. You must have an application or Web page in which you can view the controls in action, and view the source that implements them.
You do not need to modify any of a custom control's sources to support it in UFT One, but you do need to be familiar with them. For example, make sure you know what elements and attributes the control comprises, what HTML properties it has, and what events you can listen for.
Determining the Toolkit Related Information
When you plan your toolkit support set, begin by deciding the general toolkit related information:
Provide a unique name for the toolkit or environment for which you are creating support.
Decide which controls this toolkit support set will support.
UFT One displays the name of your environment in all of the dialog boxes that display lists of add-ins or supported environments. For example, when UFT One opens, it displays the name of your environment as a child of the Web Add-in in the Add-in Manager dialog box and the UFT One user can specify whether to load support for that environment.
When you design the toolkit support set, you specify this information in the toolkit configuration file. For more information, see Understanding the Toolkit Configuration File.
When planning custom support for a specific type of control, carefully consider how you want UFT One to handle controls of this type. For example, what type of test object you want to represent the controls in UFT One GUI tests, and which identification properties and test object methods you want to use. Make these decisions based on the business processes that might be tested using this type of control and operations that users are expected to perform on these controls.
You can run an application containing the custom control and analyze the control from a UFT One perspective using the Object Spy, the Keyword View, and the Record option. This enables you to see how UFT One recognizes the control without custom support, and helps you to determine what you want to change.
Note: Web Add-in Extensibility can be used to create support for Web controls within Web pages and frames. You cannot develop custom support for Web pages or frames themselves.
To view an example of analyzing a custom control using UFT One, see Analyzing the Default UFT One Support and Extensibility Options for a Sample Custom Control.
When you plan the support for a specific control, you must ask yourself a series of questions. You can find a list of these questions in Understanding the Web Add-in Extensibility Planning Checklist. When you are familiar with the questions and you are designing your own custom support classes, you can use the abbreviated, printable Web Add-in Extensibility Planning Checklist.
Where Do You Go from Here?
After you finish planning the custom toolkit support, you create the toolkit support set to support the custom toolkit as per your plan. Developing Support for Your Toolkit explains how to develop the toolkit support set.