Troubleshooting and limitations - Extensibility Accelerator

This section describes troubleshooting and limitations for Extensibility Accelerator.

In this topic:

Known issues when using Extensibility Accelerator 2022 with Google Chrome

• If you have multiple tabs open in Chrome, Extensibility Accelerator can work only with the first tab.

• Extensibility Accelerator cannot identify objects inside a frame object.

Back to top

Using Chrome with Extensibility Accelerator and OpenText Functional Testing on the same computer

Supported on OpenText Functional Testing versions 2022 and later

Extensibility Accelerator and OpenText Functional Testing currently use mutually exclusive Chrome extensions. If you install both products on the same computer, only one of them can work with Chrome at any given time. After installation, the second product you install can work with Chrome. To alternate between the products, reload the relevant Chrome extension. If you are using version 2022, you also need to update a registry key to specify the product you want to use with Chrome:

Load the relevant extension: 

Extensibility Accelerator 2022

Update the following registry key: Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Google\Chrome\NativeMessagingHosts\com.hp.uft.nativemessaginghost

Back to top

Why is the XML editor providing only generic XML IntelliSense?

If you imported your toolkit support set from another computer, the XML file might be referencing the schema file in an incorrect location.

Check the reference to the .xsd file at the beginning of your XML file (in the xsi:noNamespaceSchemaLocation attribute of the TypeInformation element).

If the reference is incorrect, do one of the following:

• Manually correct the reference to refer to the .xsd file in the correct location (in the <Extensibility_Accelerator_installdir>\dat folder).

• Remove the reference line, save the file and reopen it. Extensibility Accelerator inserts a reference to the correct schema file.

Back to top

Extensibility Accelerator supports comments in XML files only in the following situations

• The test object class designer for the test object class whose XML section you are modifying is open. (Relevant when adding comments manually. For example, if you want to add comments related to the GWTPushButton test object in the XML editor, you must also open the GWTPushButton test object class designer.)

• The comments appear directly before the opening tag of an element. However, comments before the following element types are not supported:

  • In the test object configuration file: Description, AdditionalInfo, Documentation, IdentificationProperties.

  • In the toolkit configuration file: Controls, Methods, HTMLTags, Settings, Variable (within a Controls\Settings element).

If you import a support set with XML files containing comments that are not supported, the comments are not included in the Extensibility Accelerator project's XML files. If you add such comments manually to an existing XML file in the XML editor, the comments are discarded.

Back to top

Naming Rules

In Extensibility Accelerator, Name edit boxes support only English letters, numeric characters, hyphens, and underscores, and must begin with a letter. Property names can contain spaces in addition to these characters.

If you enter unsupported characters in an edit box, they are ignored.

Back to top

Description elements inside Argument elements are not supported in the test object configuration XML file

If you import a support set with an XML file that contains these, or you add such elements manually to an existing XML file in an Extensibility Accelerator project, those elements are deleted from the XML file.

Workaround: Document argument descriptions in the Description element inside the Operation element. However, keep in mind that the operation description is displayed in OpenText Functional Testing tooltips.

Back to top

Documentation Limitations

Back to top