Introducing UFT Testing Extensibility > About UFT Testing Extensibility

About UFT Testing Extensibility

The UFT Testing Extensibility SDK provides a set of APIs that you can implement to gain full UFT functionality for your environment. To implement UFT Testing Extensibility, you create a singleton Testing Agent that interfaces between UFT and the application being tested.

From the UFT user's perspective, after you install and register the Testing Agent on a computer on which UFT is installed, the Testing Agent acts as a UFT add-in. For example, UFT displays the name of your environment in all of the dialog boxes that display lists of add-ins or supported environments. Additionally, UFT displays the list of test object classes defined by your Testing Agent in dialog boxes that display the list of test object classes available for each add-in.

The Testing Agent communicates with the application being tested and provides UFT with the information it requires about the objects in the application. UFT communicates with one Testing Agent per environment. If there is more than one instance of the application being tested at a given time, the Testing Agent must handle the multiple instances.

UFT communicates through a COM interface, therefore the Testing Agent must be a COM object. However, you can implement the communication between the Testing Agent and the application being tested in whatever way is most appropriate for your technology.

For a detailed description of the Testing Extensibility interfaces, see the UFT Testing Extensibility API Reference

Some of the information passed between the Testing Agent and UFT must conform to predefined XML schemas. For more information on the XML schemas used by UFT Testing Extensibility, see the following schema sections: TestingEnvironment, ActiveScreen, Filter, ExternalParent, Description, AppDescription, AddElements, Suppression.