Determining the Support Information for Each Custom Class

Before you begin planning the support for a custom class, make sure you have full access to the control and understand its behavior. You must have an application in which you can view the control in action, and also have access to the custom class that implements it.

You do not need to modify any of the custom control's sources to support it in UFT, but you do need to be familiar with them. Make sure you know which members (fields and methods) you can access externally, the events for which you can listen, and so forth.

When planning custom support for a specific class, carefully consider how you want UFT to recognize controls of this class—what type of test object you want to represent the controls in UFT GUI tests, which identification properties and test object methods you want to use, and so forth. The best way to do this is to run the application containing the custom control and to analyze the control from a UFT perspective using the Object Spy, the Keyword View, and the Record option. This enables you to see how UFT recognizes the control without custom support, and helps you to determine what you want to change.

To view an example of analyzing a custom control using UFT, see Analyzing the Default UFT Support and Extensibility Options for a Sample Custom Control.

When you plan your custom support for a specific class, you must ask yourself a series of questions. You can find a list of these questions in Understanding the Custom Class Support Planning Checklist. When you are familiar with the questions and you are designing your own custom support classes, you can use the abbreviated, printable Custom Class Support Planning Checklist.