IBM Rational Functional Tester (RFT): What It Is and When to Use It
IBM Rational Functional Tester, commonly called RFT, is an enterprise automation tool for testing GUI applications. It has a long history in large organizations — particularly those running IBM mainframes, Java enterprise applications, and SAP — and it remains in active use in environments where those technologies dominate.
If you're a QA engineer who's been handed an RFT license and told to make it work, or if you're evaluating automation tools for an enterprise environment, this overview covers what RFT actually does and where it fits.
What RFT Is
RFT is a record-and-playback automation tool with scriptable test cases. You can use it in two modes: recording user interactions against a running application to generate test scripts automatically, or writing scripts directly using Java or Visual Basic .NET in an Eclipse-based IDE.
The tool captures UI elements through a technology called object recognition. When you record against an application, RFT identifies and stores the properties of each UI element you interact with — a button, a text field, a menu item. During playback, it uses those stored properties to find and interact with the same elements, even if the screen layout has changed slightly.
RFT supports a wide range of application types:
- Java AWT/Swing applications
- Eclipse-based RCP applications
- Web applications (using Internet Explorer and Firefox)
- Windows applications (Win32, .NET WinForms, WPF)
- SAP GUI
- Siebel CRM
- Terminal emulators (3270, 5250)
The terminal emulator and mainframe support is significant — it's one of the reasons RFT appears in financial services, insurance, and government agencies where mainframe applications are still in active use.
How Test Recording Works
The recording process follows a consistent pattern. You start a recording session, interact with your application normally — navigating menus, entering data, clicking buttons — and RFT captures each action as a line in the test script. You can add verification points during recording by right-clicking on elements and selecting what you want to verify: the content of a field, whether a window is present, the state of a checkbox.
When you stop recording, RFT generates a script in your chosen language (Java or VB.NET). You can view and edit this script directly. The generated code is readable enough that experienced developers can modify it to add loops, conditionals, and data-driven logic.
The Object Map is a separate file that stores information about every UI element the test interacts with. When an application's UI changes — a button moves or a field ID changes — you update the Object Map rather than rewriting every test script that touches that element. This separation of UI element definitions from test logic is one of RFT's design strengths.
Data-Driven Testing
RFT supports data-driven testing through its Datapool feature. A Datapool is essentially a CSV file that feeds different values into a test script on each iteration. You create the Datapool, associate columns with variables in your test script, and RFT automatically runs the test once per row of data.
For example, a login test might have a Datapool with 20 rows of username/password combinations, with some valid and some invalid. The test runs 20 times using different credentials, verifying the correct response each time. This is more efficient than writing separate tests for each scenario.
Integrating with Other IBM Tools
RFT is part of IBM's Rational suite, which means it integrates naturally with other IBM tools your organization might be using:
IBM Rational Quality Manager (RQM) is IBM's test management platform. When you run RFT tests through RQM, results appear in RQM's test execution reports. This is how enterprise teams connect their automated tests to formal test plans.
IBM Rational ClearQuest is IBM's defect tracker (now largely superseded by Jazz/RTC). RFT can create defects in ClearQuest automatically when tests fail.
IBM Engineering Workflow Management (EWM/RTC) is the modern IBM project management tool. RFT integrates with EWM for defect tracking and build integration.
If your organization is all-in on IBM tooling, these integrations provide cohesion. If you're running a mixed environment with Jira and Jenkins, you'll need to build those integrations yourself using RFT's command-line runner and the APIs of your other tools.
Running Tests from the Command Line
For CI/CD integration, RFT provides a command-line interface. You can invoke test scripts using the ft_cmd launcher, which runs specified test scripts and returns exit codes for pass/fail. This makes it possible to include RFT tests in a Jenkins pipeline or similar CI server:
ft_cmd -datastore /path/to/project -suite MyTestSuiteThe results are written to an XML report that CI servers can parse and display as test results. The integration requires some setup, but it's workable for teams that need to include RFT tests in automated build pipelines.
Licensing and Deployment
RFT is sold on a per-seat basis as part of the IBM Rational product portfolio. It requires an IBM license server in your network, and scripts run on machines that have the RFT Eclipse IDE installed. There's no cloud-hosted version — it's an on-premises tool.
This is worth noting if you're comparing RFT to cloud-based testing tools. RFT requires infrastructure investment: license server, test execution machines, and maintenance of the IBM toolchain. That overhead is part of the cost calculation.
Where RFT Struggles
Modern web applications. RFT's web support is functional but lags behind tools specifically designed for web testing like Selenium, Playwright, and Cypress. If you're primarily testing web applications built with React, Angular, or Vue, there are better-suited tools.
Mobile testing. RFT does not support mobile application testing. You'd need to supplement it with a separate mobile testing tool.
Community and ecosystem. Unlike open-source tools, RFT has a smaller community. Finding solutions to specific problems often means IBM support documentation rather than Stack Overflow.
Script maintenance. Like all record-and-playback tools, RFT tests break when the application UI changes significantly. The Object Map helps, but high-maintenance test suites remain a common complaint.
Who Should Use RFT
RFT is a good fit when you're testing Java enterprise applications, SAP systems, or legacy mainframe interfaces that other tools can't reach. Large organizations that have been running RFT for years often continue using it because switching automation frameworks is expensive and risky, not because RFT is the best available option for their technology stack.
If you're starting a new automation program and your application is primarily web-based, there are lighter, more maintainable options to consider. But if you're inheriting an existing RFT investment or working with technology that RFT uniquely supports, there's a clear path forward.
Filling the Gaps in Production
RFT runs scheduled test suites against your application in a controlled environment. What it doesn't do is watch your production system continuously. Production has a way of breaking in between your formal test runs — deployments fail partially, certificates expire, third-party services go down.
HelpMeTest provides that continuous layer: a real browser checking your application's critical paths every few minutes, alerting your team the moment something stops working. It works alongside whatever automation framework you use for pre-release testing, covering the time between your planned test cycles.
For teams running RFT, adding continuous monitoring to your quality toolchain is a straightforward way to catch what structured test automation can't.