When planning custom support for a specific type of control, carefully consider how you want UFT One to recognize controls of this type—what type of test object you want to represent the controls in UFT One GUI tests, which identification properties and test object methods you want to use, and so on. 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.
This section also includes: