Tool Mentor: Recording a Script Using Rational Functional Tester Extension |
This tool mentor describes how to record a script using Rational Functional Tester Extension.
Tool: IBM Rational Functional Tester Extension
Relationships
Related Elements | Develop Test Identify Targets of Test
Main Description
### Overview Rational Functional Tester Extension for Terminal-based Applications (FTE) is used to automate the testing of MVS, VM, OS/400 and Unix host applications. This tool mentor assumes you have installed the Rational Functional Tester Extension and have some familiarity with Rational Functional Tester (RFT). This tool mentor describes how to record a simple RFT script that uses FTE to connect to a host system. #### Tool Steps Begin the script creation by opening a Rational Functional Tester project and recording a test script. From the RFT project, use the menu bar or toolbar to start recording a script. From the RFT "Recording" window toolbar, press the "Start Application" button and select "Extension for Terminal Applications" to bring up FTE. Enter the host connection configuration information, either manually or by loading a saved connection configuration file. [ref to fte_save_and_load_connection_config Tool Mentor] Press the "Connect" button and login to your host system. Perform the host actions you want to test. Logoff from the host and close the FTE window. You may now stop recording of the script. To run the script, open your RFT project, select the script, and press the "Run Functional Test Script" button. Upon completion of the test script, RFT will bring up a browser window with the results of running the tests, including the verification points. When recording a script, it can be helpful to use the "Wait for Test Object" feature of the RFT "Verification Point and Action Command" to explicitly wait for each new window that is created. When the script is played back, the speed at which it executes can vary, so waiting for the objects to be created can help keep the script actions in synchronicity with the objects being created and modified on the desktop. For cases that cannot be solved by waiting for an object to be created, you might be able to synchronize the script with the desktop by editing the test script to insert sleep() statements. The argument to the sleep() method is in seconds.
© Copyright IBM Corp. 1987, 2009. All Rights Reserved.