Troubleshooting functional tests in Google Chrome browsers

If you encounter problems while testing in Google Chrome browsers, you will find useful information in this section to resolve them.

The Google Chrome browser is not properly enabled
It is not possible to record on a Google Chrome browser
Actions are recorded on the Windows domain and not in the application domain
Problems with playing back certain actions

The Google Chrome browser is not properly enabled

If the error CRFCN0794E is displayed when you try to record on a Google Chrome browser, the browser is not properly enabled. This can be due to one of the following reasons:

No Sun Java Runtime Environment (JRE) was associated with the browser, or the associated JRE was not enabled. To resolve this, associate Sun JRE 1.6 Update 10 or later with the Google Chrome browser, and then verify that the browser has been enabled by opening the Enable Environments dialog box in Rational® Functional Tester.
The default web server port (9100) for communication between the Google Chrome browser and Rational Functional Tester is being used by another application on the workstation. Change the default port and specify an available port in both the Webserver Configuration page in the Rational Functional Tester Preferences dialog box, and in the Options for the IBM® Rational Functional Tester for Google Chrome™ extension. For instructions to do this, see the related topics Changing the web server port for communication with Google Chrome and Webserver Configuration page.
Note: Ensure that you specify the same port number in both places.

It is not possible to record on a Google Chrome browser

This problem could occur due to one of the following reasons:

The browser was not properly enabled. Ensure that the browser is properly enabled.
The browser was started with a blank home page, that is, without a home URL. To prevent this, always specify a home URL for the Google Chrome browser.

Actions are recorded on the Windows domain and not in the application domain

While recording on Google Chrome browsers, actions on objects in the test application may be recorded in the Windows domain and not in the application domain. This can occur due to one of the following reasons:

The action was recorded before the document was loaded completely in the Google Chrome browser. To prevent this, record an action on an application page only after the document has loaded completely.
The browser was started before either Rational Functional Tester or the recording monitor was started. To prevent this, always start the browser only after you have started either Rational Functional Tester or the recording monitor.
Actions on controls in dialog boxes are recorded as click(atPoint()) relative to the dialog box. To prevent this, use keystrokes to record on dialog box controls.

Problems with playing back certain actions

Some actions recorded on Google Chrome browsers need the script to modified, to be played back successfully. For example

Clicking the Back and Forward buttons in the browser. To play back these actions, modify them in the recorded script using the browser-level back() and forward() APIs.
Actions on combo box drop-down controls. To play back these actions, modify the script manually and specify the option that must be selected during playback.

Feedback