Release notes for Rational Functional Tester 10.0.1
Description
IBM Rational Functional Tester is an automated testing tool that tests a broad range of applications, such as:
- HTML5-based web applications built on modern frameworks, such as Angular, React and Vue.js in the latest versions of the world’s popular browsers, both on the desktop and mobile devices
- Legacy HTML applications
- Java™ and .Net-based thick client applications
- ERP systems such as SAP
- IBM zSeries, IBM iSeries, IBM pSeries, and mainframe applications
- Ajax, Microsoft Windows, Microsoft .NET, Microsoft Silverlight, Microsoft Visual Basic, Siebel, Flex, GEF, and PowerBuilder applications
- Adobe PDF documents
You can also import and work with Selenium tests and combine tests of various types into compound tests.
To view the full list of domains, software, and platforms that are supported for functional testing and the compatible versions of Rational products that can be integrated with Rational Functional Tester, see Software Product Compatibility Reports.
Some of the older versions of software supported by Rational Functional Tester are deprecated. To view the list of deprecated software, see http://www.testworkbench-community.com/blogs/technology-currency-updates-for-rational-functional-tester-92.
Integrated Development Environments
Rational Functional Tester is available in two integrated development environments (IDE): Eclipse and Microsoft Visual Studio .NET. The Eclipse integration supports both Java and simplified (non-programming) method of scripting while the Microsoft Visual Studio .NET integration supports Microsoft Visual Basic .NET scripting language.
What's new in 10.0.1
- Support to replace dataset values during a test run by using the command-line interface. Therefore, when you run a test by using the command line, the values are substituted from the new dataset instead of the original dataset. See Running a test from a command line.
- Support to specify or generate a log file for each test when multiple tests are run from the command line. The tests are executed in sequential order when you run multiple tests from a command line. See Running a test from a command line.
- Support to integrate the product with Micro Focus Application Lifecycle Management to run test scripts as part of application development and testing cycle. You can use ready-made templates available in the product installation directory to add the details of your test script and run them in Micro Focus Application Lifecycle Management. See Integrating and running Functional Test scripts in Micro Focus Application Life Cycle Management and Integrating and running Web UI Test scripts in Micro Focus Application Life Cycle Management.
- Support to remove offline user tokens added to the workbench. As a result, multiple users can publish reports to the same Rational Test Automation Server with a different role. See Publishing test results to the server.
- Support to apply self-healing to compound tests. You can now use self-healing to automatically update the test steps in a compound test. See Using guided healing and self-healing features to update test scripts.
- Support to indicate whether a test step is passed through guided healing feature using Mobile and Web UI report. See Using guided healing and self-healing features to update test scripts.
Installing the product
For installation instructions, see Installing Rational Functional Tester.Rational Functional Tester is available as a standalone product and is also included with Rational Test Workbench. You can use the same license key for each installation.
Known limitations and workarounds
- When you upgrade Rational Functional Tester from V10.0.0 to V10.0.1 on RHEL, you can ignore and close the error message, "VM terminated. Exit Code=1", which displays during the installation to proceed as it does not have any impact on the product functionality.
- When you install Rational Functional Tester V10.0.1 by using the launchpad program, a script error is displayed. You must close the dialog box to proceed with the installation.
- Known problems are documented in the fix list and download document. Select a fix list from http://www-01.ibm.com/support/docview.wss?uid=swg27036170. From the fix list, you can view the download document for additional information.
- Known problems are also documented in the form of individual technotes in the Support Knowledge Base. For more information, see All technotes for Rational Functional Tester.
After playing back a script in Rational Functional Tester, a message such as the following is displayed in the console: The IBM Class Sharing Adaptor will not work in this configuration. You are not running on a J9 Java VM. This message is displayed because the version of Eclipse that is used in the IDE is from IBM and has the IBM Java optimizations enabled. To resolve the issue:
- Navigate to the Rational Functional Tester Plugins Shared Folder.
- Back up the com.ibm.cds plugin and delete it.
- Restart Rational Functional Tester.
Contacting IBM Software Support
IBM Software Support provides you with technical assistance.
For FAQs, lists of known problems and fixes, and other support information, visit the product support page for Rational Functional Tester software.
For product news, events, and other information, visit the product home page for Rational Functional Tester Software at https://www.ibm.com/us-en/marketplace/rational-functional-tester.
Before you contact IBM Software Support, gather the background information that you need to describe your problem. When you are describing a problem to an IBM Software Support specialist, be as specific as possible and include all relevant background information so that the specialist can help you solve the problem efficiently. To save time, know the answers to these questions:
- What software versions were you running when the problem occurred?
- Do you have logs, traces, or messages that are related to the problem?
- Can you reproduce the problem? If so, what steps do you take to reproduce it?
- Is there a workaround for the problem? If so, be prepared to describe the workaround.