If Internet Explorer 9 displays the message: Speeding up browsing by disabling add-ons, choose Don't disable or select a bigger threshold value.

Creating and running steps that start an InPrivate Browsing session is supported only by using Tools > InPrivate Browsing.

Using toolbars or extensions for this operation may cause Internet Explorer to behave unexpectedly.

Creating and running steps that are related to tabs, such as selecting a tab or creating a new tab is not supported when Internet Explorer is in Full Screen mode.

Workaround: Add a <Browser>.FullScreen step before and after the relevant step to switch the Full Screen mode.

Recognition of test objects when using AutoXPath is very slow for web pages in Quirks Mode and Almost Standards Mode.

Workaround:

Convert the web page into Standards Mode by doing one of the following:

• Add or change the DOCTYPE of the page.

  Add or change it into one of the following:

  <!DOCTYPE.htlm>

  <!DOCTYPE.HTML PUBLIC "-//W3C//DTD HTML 4.01//EN""http://www.w3.org/TR/html4/strict.dtd"

• Disable AutoXPath capabilities in OpenText Functional Testing.

  Clear the Learn and run using automatic XPath identifiers option in the Web > Advanced pane

  (Tools > Options > GUI Testing tab > Web > Advanced node).

When using the RunScript or RunScriptFromFile methods, Alert, Confirm, or Prompt dialogs are not displayed.

Workaround: When writing a RunScript method, use the following method syntax:

Set wnd=Browser("<browser name>").Page("<page name>").RunScript("window") wnd.alert()

or

Browser("<browser name>").Page("<page name>").RunScript "setTimeout(function () {alert(); }, 0)"

The WebXML test object is not supported on Internet Explorer 9 or later running in standard mode.

Accordingly, features related to WebXML test objects, such as XML checkpoints and output value steps, are not supported on such browsers.

In some cases, OpenText Functional Testing does not support or recognize about:blank tabs in Internet Explorer 11.

The Type property of the WebButton test object that uses the HTML <button> tag has a different default value in Internet Explorer and Chrome/Edge/Firefox.

In Internet Explorer the default value is Button, but in Chrome/Edge/Firefox the default value is Submit.

Workaround: Do not use the Type property in the description of a WebButton test object.

When using Internet Explorer 9, the innertext, outertext, innerhtml and outerhtml property values may differ from earlier versions of Internet Explorer.

Therefore, using these values in parameters or running checkpoints that use these property values may cause the steps to fail.

Sometimes, the Browser.Back step may not be performed if its previous step causes a page redirection.

Workaround: Add a Wait statement between the two steps.

Example:

Browser("Advantage Shopping").Page("Advantage Shopping").WebElement("SpeakersCategoryTxt").Click

Wait 2

Browser("Advantage Shopping").Back

Active Screen

When recording a test on Internet Explorer 8 or earlier with the Active Screen enabled, performance on the site may become very slow.

This is due to a performance issue in the JavaScript engine used in these browsers.

Workaround: Record the test using Internet Explorer 9, or disable the Active Screen.

For details, see the OpenText Functional Testing User Guide.

Drop-down boxes in a web page

OpenText Functional Testing may respond slowly during a recording session if the drop-down boxes in a Web page contain a lot of data.

Workaround: Learn the objects on a Web page that contains a lot of data (instead of recording).

Oracle ADF

Recording on an Oracle ADF object in Internet Explorer may result in performance issues.
If this occurs, use a different browser to record, or create the script manually.

Switching between internet and intranet sites

OpenText Functional Testing does not record steps when switching between an Internet site and an Intranet site, if you are using Internet Explorer with:

• UAC enabled

• Protected mode enabled for either the Internet zone or the Intranet zone (Internet Options > Security tab)

• Protected mode disabled for the other zone (the Internet or Intranet zone)

Workaround: Set the integrity level (Protected mode enabled or not enabled) to be the same for the Internet and Intranet zones.

Customized toolbar buttons

OpenText Functional Testing records only on the toolbar buttons displayed by default in Internet Explorer, and does not record on customized toolbar buttons.

Find window

OpenText Functional Testing does not record on the Find window of the Internet Explorer browser.

Auto-complete operations

In Internet Explorer, the AutoComplete operation on edit fields is not recorded.

Workaround: You can deactivate the AutoComplete feature in Internet Explorer by selecting Tools > Internet Options > Advanced and deselecting the Use inline AutoComplete under the Browsing options in Internet Explorer.

Specific SAP objects and methods

Recording the following methods in Internet Explorer may have unexpected results:

• SAPUIDateTimeInput.SetDateTime (Fiori 1.52)

• SAPWebExtTable.SetCellData

Workaround: If your script is not recorded correctly, do one of the following:

• During recording, click elsewhere to clear the selection on the object, and then click the object again to select it. Then perform the operation again to record it.
• Edit the script manually.
• Record using a different browser.

If you record a click on an area of an image map that is not mapped to a URL in Internet Explorer, OpenText Functional Testing will perform a click on the first mapped area of that map during the run session.

When recording on an combo box object in which the role property is "listbox" (and is recorded as a WebList object), OpenText Functional Testing adds additional WebEdit.Set steps to the test when you select a value from the object with the .Select method.

Workaround: Delete the unneeded WebEdit.Set steps.

Recording on web pages built in Angular is not supported in Internet Explorer.