UFT 12 - Troubleshooting and Limitations of Mozilla Firefox

General Limitations :

·         If two minor versions of Mozilla Firefox are installed on the same computer, and the earlier version was installed after the later version, UFT may not recognize which is the latest version.

·         UFT does not support anonymous content elements in non-XUL frames. (For example, the buttons in the Mozilla Firefox SSL exception page.)

Recording :

·         Recording on Mozilla Firefox pages is only possible when the page is fully loaded.

·         When recording steps in Mozilla Firefox, additional steps may be recorded.

Workaround: Manually remove the extraneous steps after the recording session ends.

·         When recording on some Mozilla Firefox versions, if you perform a search on google.com by entering the search string and then pressing Enter, the Submit operation is not recorded. Subsequently, when you run the test, UFT enters the search string but does not perform the search.

Workaround: Do one of the following:

• When recording the search operation, click the search button instead of pressing Enter.

• Manually add the Submit (or Click) step to the test or component.

·         The If Handler option in the Web Event Recording Configuration Dialog box works on Mozilla Firefox browsers only if the handler is assigned as an attribute (for example, <A onclick = "some code"/>) and not if it is assigned as a property (for example, aObj.onclick = function() {some code})

Test Objects, Methods, Properties, and Checkpoints :

·         UFT does not support accessing browser dialog boxes (such as alert, confirmation, or prompt) directly in Mozilla Firefox.

Workarounds for Firefox only:

o    Use the HandleDialog or GetDialogText methods described in the Web section of the HP UFT Object Model Reference for GUI Testing.

o    If the Browser("xxx").Dialog("xxx").Page("xxx") object is recognized, either use a recovery scenario with the HandleDialog method, or a Browser("xxx").Dialog("xxx").Page("xxx").Type step to handle the pop-up dialog box. For example, use an Enter key to click the default button and close the dialog box.

·         The Object Spy and Checkpoint Properties dialog boxes do not retrieve the current value of edit boxes in Mozilla Firefox dialog boxes.

·         The Object Spy and Navigate and Learn dialog boxes do not retrieve the current value of tabmodal dialogs in Mozilla Firefox.

·         The Type property of the WebButton test object has a different default value in Microsoft Internet Explorer and Mozilla Firefox. In Microsoft Internet Explorer the default value is Button, but in Mozilla Firefox the default value is Submit.

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

·         When using Mozilla Firefox, the innertext, outertext, innerhtml and outerhtml property values may differ from other browsers. Therefore, using these values in parameters or running checkpoints that use these property values may cause the steps to fail.

·         The following test objects, methods, and other Web-specific functionalities are not supported in Firefox:

o    ViewLink test object

o    WebXML test object (and, accordingly, XML checkpoints and output value steps)

o    Browser.Object method

·         Text area checkpoints are not supported on Mozilla Firefox.

·         If you drag a tab to create a separate window in Firefox, UFT stops recognizing, recording, or running any web objects in the new window.

Web 2.0 Support :

·         Due to synchronization issues, if you navigate to a new Web page in Firefox while recording, then UFT may not record certain operations on certain ASP.NET Ajax or jQuery UI objects in the page. Similarly, when running steps that navigate to a new page, UFT may fail to perform certain steps on certain ASP.NET Ajax or jQuery UI objects.

Workaround: If the problem occurs while recording, refresh the Web page and record the step again. If the problem occurs while running, insert a Wait() statement before the problematic step.