Working with an Extensibility Testing Agent

This section provides information about how OpenText Functional Testing behaves when working with an OpenText Functional Testing Extensibility Testing Agent. You may want to include some of this information in the user documentation that you provide for your Testing Agent.

Loading the Testing Agent

When OpenText Functional Testing opens, it checks for registered Testing Agents and displays their environments in the Add-in Manager. The OpenText Functional Testing user can select an add-in, which instructs OpenText Functional Testing to load support for that environment by creating the Testing Agent COM object. For more information on the Add-in Manager dialog box, see the OpenText Functional Testing Help Center .

If the Testing Agent's environment display name is unique, the Testing Agent can also be loaded using an OpenText Functional Testing automation script. This is done by calling the SetActiveAddins method and providing the environment display name in the AddinNames argument.

This argument must be the same as the name that you provide in the following locations:

The szEnvDisplayName argument of the RegisterTeaAut method, which is used to register the Testing Agent.
The AddinName attribute of the TypeInformation element in the testing environment XML.

This name is displayed in the Add-in Manager dialog box when OpenText Functional Testing opens. For more information on the SetActiveAddins method, see the UFT Automation Object Model Reference.

If support for an environment is loaded:

OpenText Functional Testing recognizes the controls in that environment and can run tests on them.
OpenText Functional Testing displays the environment display name in all of the dialog boxes that display lists of add-ins or supported environments. (For example: Define New Test Object dialog box, Object Identification dialog box.)
OpenText Functional Testing displays the list of test object classes defined in the testing extensibility XML in dialog boxes that display the list of test object classes available for each add-in or environment.

Using the Object Identification Dialog Box

The OpenText Functional Testing user cannot modify the set of identification properties that comprises the test object description, which is defined in the testing environment XML. Therefore, when the OpenText Functional Testing user selects an environment supported by a Testing Extensibility Testing Agent in the Object Identification dialog box, the buttons for adding and removing properties and the Ordinal identifier option are disabled.

Configuring and Using Smart Identification

In the Object Identification dialog box, the OpenText Functional Testing user can select a test object class that belongs to an environment supported by Testing Extensibility and configure its properties for Smart Identification. For information on configuring Smart Identification, see the OpenText Functional Testing Help Center .

When no object in the application matches the description stored in the test, OpenText Functional Testing uses Smart Identification (if it is configured) to try to identify the object in the application.

To enable OpenText Functional Testing to use the Smart Identification mechanism to single out the correct object when more than one object matches the description, the Testing Agent must implement FindObjectId2. For more information, see Implementing FindObjectId or FindObjectID2: Map a Description to an Object ID.

Configuring and Using the Object Identification Center

Supported on OpenText Functional Testing versions 15.0.2 and later

Object Identification Center (OIC) is a next-generation Object Spy. Using the OIC, you can spy on multiple visible objects in an open application at a time and create unique descriptions for them. To enable OpenText Functional Testing to use the OIC to spy on applications created based on TEA, you must customize the spyProps.json file located in the OpenText Functional Testing Installation folder\dat path.

Before you open the OIC, add the following configuration to the spyProps.json file.

Copy code

"TEAHoursReportSamplePackage": {
              "DemoApp": {
                              "addInName": "TEAHoursReportSample",
                              "propertiesToShow": []
              },
              "DemoButton": {
                              "addInName": "TEAHoursReportSample",
                              "propertiesToShow": []
              },
              "DemoList": {
                              "addInName": "TEAHoursReportSample",
                              "propertiesToShow": []
              },
              "DemoReportWorkingHours": {
                              "addInName": "TEAHoursReportSample",
                              "propertiesToShow": []
              },
},

Troubleshooting and Limitations