Release notes for IBM® Rational® Functional Tester

Automatic selection of the Web UI engine to run functional test scripts

Rational® Functional Tester now automatically selects the Web UI engine as a default feature when you play back functional test scripts. The Play back with Web UI Extension and Play back with Web UI Action checkboxes in Window > Preferences > Functional Test > Playback are selected as default options after you install or reinstall Rational® Functional Tester. See Playback of test scripts for HTML applications by using the Web UI engine.

Enhancement to an IF condition comparison

Rational® Functional Tester is now enhanced to perform a digit comparison when you apply an IF condition to a test. If the digit comparison in the IF condition is successful, the result is displayed as true. Otherwise, it is displayed as false. See Adding conditional logic to tests.

Enhancement to the command line option

Previously, to run all the test assets from the specified folder path, you created a batch file and ran the test from the command line. The command line option is now enhanced so that you can run multiple test assets at a time by using the wildcard character * enclosed in quotes. You can use * in different combinations to specify any or all test assets that are in a folder. See Running multiple tests from the command line and Configuration of test runs from the command line.

Enhancements to the Details panel of unified reports

You can now view the profile name and clear cache and clear history values in the Start application section of the Details panel in the unified reports after the test playback. You can now also view the delete cookies information as a step in the Details panel. This enhancement is applicable for the playback with the Web UI engine for HTML applications. See Unified reports.

Support to add the drag-and-drop action in Web UI tests

You can now edit the test steps to add the drag-and-drop action for UI elements in the Web UI tests. See Adding the drag-and-drop action in a Web UI test.

Support to add user actions that use the keyboard shortcuts

You can now add text-related user actions that use the combination of special keys such as SHIFT or CTRL along with other keys in the functional tests that are run by using the Web UI engine.

Support to check if Javascript dialogs exist on a web page

You can now add test steps to check if any dialog such as alert, confirm, or prompt is present on a web page, and then choose to report the test step as Pass. If you choose to report the test step as Pass, the test moves successfully to the next step, although the dialog does not exist. You can view the unified report to read the message that is logged regarding the presence of the dialog. See Creating verification points for alert, confirm, or prompt dialogs.

Support to run tests or resources as a GitHub Action

You can now run tests or resources that are contained in your project in Rational® Functional Tester as a GitHub Action from a Git repository.

See Configuration of test runs as a GitHub Actions Workflow in the UI Test perspective and Configuration of test runs as a GitHub Actions Workflow in the Functional Test perspective.

Support to use the Exist property on Web UI tests

By enabling the Verify and Retry options, you can now use the Exist property for a control, so that if the control takes longer than the expected time to appear or disappear on the AUT during the test playback, then Rational® Functional Tester can wait until the control appears or disappears to perform actions.

Additionally, you can now assign the Exist property to a variable in the test, and you can use conditional statements if you want to perform certain actions on the AUT depending on the presence or absence of the control. See Creating verification points for objects in tests and Assigning a test variable to an object property.

Using regular expressions to assign dynamic values to variables

You can now extract a substring from the content of an object's property by using a regular expression and then assign the substring to a variable. You can view the variable value in the unified report. See Assigning a test variable to an object property.