About OpenText Functional Testing Extensibility

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

From the OpenText Functional Testing user's perspective, after you install and register the Testing Agent on a computer on which OpenText Functional Testing is installed, the Testing Agent acts as an OpenText Functional Testing add-in. For example, OpenText Functional Testing displays the name of your environment in all of the dialog boxes that display lists of add-ins or supported environments. Additionally, OpenText Functional Testing 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 OpenText Functional Testing with the information it requires about the objects in the application. OpenText Functional Testing 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.

OpenText Functional Testing 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 OpenText Functional Testing Extensibility API Reference

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