Understanding Custom Support Classes

In a custom toolkit support set, there is a custom support class for each supported custom class. The custom support class provides the actual interface between the custom class methods and the UFT capabilities, thus providing the UFT Java Add-in Extensibility.

A single custom support class can provide support for more than one custom class. The support class can be mapped (in the toolkit configuration file) to more than one custom class. This support class then provides support for the custom classes that are mapped to it, and for their descendants.

The first step in creating the support classes is determining the class inheritance hierarchy. This includes deciding the order in which you create support for classes within the custom toolkit, and determining which existing support class the new support class must extend.

The second step is deciding what test object class to map to the custom control.

After you make the preliminary decisions regarding hierarchy and test object class, you are ready to write the main part of the UFT Java Add-in Extensibility—the custom support class.

Each custom support class determines what test object class is mapped to the custom control it supports and how the identification properties and test object methods are implemented.

The custom support class inherits the methods of its superclass. You can use the super implementation, override the methods, or add new ones, as needed. In support classes, you use the following types of methods:

When you implement these methods in the custom support class, you can use different methods supplied in the MicAPI. For more information, see Using Methods from MicAPI and the API Reference.

For a short summary of the types of methods a custom class contains, see Support Class Summary.