With IBM® Rational® Functional Tester,
you can test HTML applications that are loaded in Google Chrome browsers
in Microsoft Windows environments.
You can test HTML applications that contain the following controls:
- HTML controls
- Dojo controls in applications built using Dojo Toolkit versions 1.0, 1.1, 1.2, 1.3.2, 1.4.2,
1.5, 1.6.1, 1.7, 1.8, and 1.9
- Applets
You can also perform the following actions:
- Test HTML applications that are loaded in multiple browser windows
or embedded frames and inline frames, with varying zoom levels
- Record a functional test script in a Microsoft Internet Explorer or Mozilla
Firefox browser and play it back in a Google Chrome browser, provided
that the Document Object Model (DOM) is compatible with the Google
Chrome browser.
- Record a functional test script in a Google Chrome browser and
play it back in a Microsoft Internet
Explorer or Mozilla Firefox browser, provided that the Document Object
Model (DOM) is compatible with the other browsers.
- Use the manual scripting find() method while testing applications
in a Google Chrome browser. To use the manual scripting find() method,
a browser instance is required. The browser instance is returned only
after the document is completely loaded and not when the browser starts.
Support for functional testing in Google Chrome browsers is version
independent, so you can test HTML applications in any version of a
Google Chrome browser. Support has been validated up to Google Chrome
23.0.
The IBM Rational Functional Tester for
Google Chrome™ extension
To perform functional testing in Google Chrome browsers, an extension is required to be added to
the browser that enables communication between
Rational Functional Tester and
Google Chrome browsers through a web server. This extension, known as
IBM Rational Functional Tester for
Google Chrome™, is available with your
Rational Functional Tester
installation. Alternatively, it is also available on the Google Chrome web store. To test
applications loaded in Google Chrome, you must enable the browser.
Note: If you have Google Chrome version 33 or later, you must download the Rational Functional Tester for
Google Chrome extension from Chrome web store. If you already had the extension and then you
upgraded to Chrome version 33 or later, you must uninstall the extension and install it again from
the Chrome web store.
Prerequisites for functional testing in Google Chrome
browsers
Before you use
Rational Functional Tester to
test applications on Google Chrome browsers, complete these procedures:
- Ensure that you have installed the Sun Java Runtime Environment
(JRE) 1.6 Update 10 or later, and that the JRE is associated with
the Google Chrome browser.
- In the Google Chrome browser settings, ensure that extensions
are allowed, and that both Java and JavaScript are also allowed. Do
not change the default browser settings.
- Enable the browser manually for functional testing. To do this,
complete one of the following steps:
- Enable the browser manually from the Enable Environments dialog
box in Rational Functional Tester.
The browser opens and you are prompted to add the IBM Rational Functional Tester for
Google Chrome extension to the browser. For instructions to enable
the Google Chrome browser manually, see the related task named Enabling
Google Chrome browsers.
- Add the IBM Rational Functional Tester for
Google Chrome extension to the browser from the web store. Verify
that the browser is enabled by using the Enable Environments dialog
box in Rational Functional Tester.
For instructions to add the extension from the web store, see the
related task named Adding the extension IBM Rational Functional Tester for
Google Chrome. Ensure that you have an Internet connection to access
the extension from the Google Chrome web store.
- The default web server port for communication between Google Chrome
and Rational Functional Tester is
set on the Webserver Configuration page in the Preferences dialog
box, as well as in the options for the IBM Rational Functional Tester for
Google Chrome extension. If this default port number is in use, you
must specify an available port. Ensure that you specify the same port
in both the Preferences dialog box as well as
in the options for the extension.
- Ensure that you start Rational Functional Tester before
you start the application-under-test (AUT) in the Google Chrome browser.
After you start Rational Functional Tester,
open the AUT by completing one of the following steps:
- Configure the AUT in the Application Configuration Tool in Rational Functional Tester and
start the application from there. Alternatively, you can start the
AUT at the time of recording by using the Start Application icon on
the recording toolbar.
- To start the Google Chrome browser independent of Rational Functional Tester,
append -allow-outdated-plugins -allow-file-access-from-files
-always-authorize-plugins to the Google Chrome shortcut,
and then start the browser.
Points to remember while testing in Google Chrome
browsers
- Record an action on an application page only after the document
has loaded completely.
- Ensure that you start the browser only after you start either Rational Functional Tester or
the recording monitor.
- To record and play back on local files that can be opened in a
Google Chrome browser, ensure that you select the Allow
access to file URLs check box in the extensionIBM Rational Functional Tester for
Google Chrome™.
- Recording on the Back and Forward buttons in the browser are not
supported. Use browser-level back() and forward() APIs
to play back these actions.
- When you record a script, actions on controls in dialog boxes
are recorded as click(atPoint()) relative to
the dialog box. You can also use keystrokes to record on dialog box
controls.
- Playback of actions on combo box drop-down controls is not supported.
To play back these actions, modify the script manually and specify
the option that must be selected during playback.
- The browser-level deletecookies() API is
not supported. Cookies must be deleted manually.
- Recording on tabs is not supported.
- Recording on applications built using Dojo toolkit might be slow
compared to other browsers such as Microsoft Internet
Explorer or Mozilla Firefox.
- Recording and playback is not supported in Google Chrome browsers
in cases where the browser is started with a blank home page, that
is, without a home URL.