Explore topic-wise InterviewSolutions in .

RFT Stands for Rational Functional Tester, It’s an IBM Product.IBM’s Rational Functional Tester is most powerful next GENERATION functional-testing and automation tool from Rational and is based upon object-oriented TECHNOLOGY. Due to its extreme SIMPLICITY & robustness, it is in GREAT demand all across the industry involved in Application Development & Testing.

It is an Automation Testing tool used for Automation and regression testing. 

RFT Stands for Rational Functional Tester, It’s an IBM Product.IBM’s Rational Functional Tester is most powerful next generation functional-testing and automation tool from Rational and is based upon object-oriented technology. Due to its extreme simplicity & robustness, it is in great demand all across the industry involved in Application Development & Testing.

It is an Automation Testing tool used for Automation and regression testing. 

When we ASSOCIATE Rational Functional TESTER project with a Rational project, we can use Test MANAGER to run the RFT scripts on computers that are designated as Agent computers from a single Windows COMPUTER called the Local computer.

When we associate Rational Functional Tester project with a Rational project, we can use Test Manager to run the RFT scripts on computers that are designated as Agent computers from a single Windows computer called the Local computer.

Using PLAYBACK monitor, during the playback of script; we can view the script name, NUMBER of the line that is executing, status icons and a DESCRIPTION of the action in PROGRESS.

Using playback monitor, during the playback of script; we can view the script name, number of the line that is executing, status icons and a description of the action in progress.

• Restore testing environment and set playback options.
• Play back TEST script against a new BUILD of the APPLICATION under test.
• Analyze the test results in the Rational Functional Tester LOG.
• Use the Rational Functional Tester Verification Point Comparator to determine the cause of verification point failures.
• If required, revise your test SCRIPTS to use new features in the application under test and playback the revised test scripts.

TEST DEVELOPMENT PHASE and REGRESSION TESTING Phase

Test Development Phase and Regression Testing Phase

• Restore test environment and SET the playback options.
• Play back each script against the same version of the application under test that was used for recording.
• Analyze the results in the Rational Functional TESTER log.
• Use Functional Tester Verification Point Comparator for determining the cause of verification point failures.
• If the script fails; then edit it or debug it or re record it so that it runs as REQUIRED.
• If we associate a Rational Functional Tester project with the current Rational project, we can GROUP various SCRIPTS into test suite and play back the suite to verify that the scripts work properly.

HOVER FEATURE is useful to move the mouse towards a PARTICULAR place during playback in HTML application. It is helpful for clicking on menus or LINKS in HTML TESTING.

Hover feature is useful to move the mouse towards a particular place during playback in HTML application. It is helpful for clicking on menus or links in HTML testing.

Standard WAY: ScriptAssure Page - Standard controls object-matching SENSITIVITY during playback by using a slider CONTROL.

ADVANCED way: The ScriptAssure Page - Advanced sets thresholds for recognition scores. You can set a maximum score to CONSIDER a test object as a candidate for recognition.

Standard way: ScriptAssure Page - Standard controls object-matching sensitivity during playback by using a slider control.

Advanced way: The ScriptAssure Page - Advanced sets thresholds for recognition scores. You can set a maximum score to consider a test object as a candidate for recognition.

This feature helps the successful playback of scripts EVEN when the application under test has been updated. We can play BACK scripts in RFT by using the ScriptAssure feature to control object-matching sensitivity.

For RFT to RECOGNIZE an object in the application-under-test, the object properties must match the properties recorded in test object map. RFT can find the object if 1 or 2 properties do not match. If 2 properties do not match, RFT gives a WEAK recognition warning to the log. If more than 3 properties do not match, RFT cannot find the object in the application.

This feature helps the successful playback of scripts even when the application under test has been updated. We can play back scripts in RFT by using the ScriptAssure feature to control object-matching sensitivity.

For RFT to recognize an object in the application-under-test, the object properties must match the properties recorded in test object map. RFT can find the object if 1 or 2 properties do not match. If 2 properties do not match, RFT gives a weak recognition warning to the log. If more than 3 properties do not match, RFT cannot find the object in the application.

Java SCRIPTING / VB.NET Scripting. On a remote computer, you need to install Rational Test Agent software on the Agent computer and start the agent.

However, if we need external library to run scripts, then we need to install the software on the system on which we plan to run the SCRIPT. To install a .dll, you need to add the library to directory that is in system SEARCH paths and to install a .jar file, you will need to add it to the Functional Tester customization directory. DEFAULT location for the customization directory is: C: Documents and Settings All Users Application DataIBMRFTcustomization

Java Scripting / VB.NET Scripting. On a remote computer, you need to install Rational Test Agent software on the Agent computer and start the agent.

However, if we need external library to run scripts, then we need to install the software on the system on which we plan to run the script. To install a .dll, you need to add the library to directory that is in system search paths and to install a .jar file, you will need to add it to the Functional Tester customization directory. Default location for the customization directory is: C: Documents and Settings All Users Application DataIBMRFTcustomization

• RUNNING the scripts on more than ONE COMPUTER.
• Test different machine configurations.
• Run Functional Tester scripts REMOTELY on Linux or Windows computers.

Record Monitor goes BLANK while RECORDING against JAVA or HTML application when JREs or browsers are not ENABLED.

Record Monitor goes blank while recording against Java or HTML application when JREs or browsers are not enabled.

THREE ways: Save the CURRENT TEST script or FILE, Save all test scripts & files and Save a script under ANOTHER name

Three ways: Save the current test script or file, Save all test scripts & files and Save a script under another name

There are two TYPES of DATAPOOLS: PRIVATE datapool and SHARED datapool

There are two types of datapools: Private datapool and Shared datapool

OBJECT FINDER Tool METHOD and TEST Object BROWSER method

Object Finder Tool method and Test Object Browser method

During data driven testing, the script uses variables for KEY application input fields and programs instead of literal VALUES so that we can use external data to DRIVE the application being TESTED. Data driven testing uses data from an external FILE called as datapool. We can add data to the data pool after finishing the recording of the test script.

During data driven testing, the script uses variables for key application input fields and programs instead of literal values so that we can use external data to drive the application being tested. Data driven testing uses data from an external file called as datapool. We can add data to the data pool after finishing the recording of the test script.

When we rename a script, RATIONAL Functional Tester renames all its related files like the helper script files, private OBJECT MAP and any verification point files. If you rename a test object map, the ASSOCIATED scripts with the new name gets UPDATED.

When we rename a script, Rational Functional Tester renames all its related files like the helper script files, private object map and any verification point files. If you rename a test object map, the associated scripts with the new name gets updated.

In RFT, this FEATURE is used to set wait state for an object during the playback to check its existence. It is useful when WAITING for an object after starting the application or after other ACTIONS TAKING a long time.

In RFT, this feature is used to set wait state for an object during the playback to check its existence. It is useful when waiting for an object after starting the application or after other actions taking a long time.

It is used to get a display of the test object information in running application. The information can be of parent HIERARCHY, inheritance hierarchy, test object properties, non-value properties and method information. Test Object Inspector automatically tracks the CURSOR and performs live updates after the application is OPENED. Test Object Inspector does not capture the object / OBJECTS in the application if it is not active.

It is used to get a display of the test object information in running application. The information can be of parent hierarchy, inheritance hierarchy, test object properties, non-value properties and method information. Test Object Inspector automatically tracks the cursor and performs live updates after the application is opened. Test Object Inspector does not capture the object / objects in the application if it is not active.

SEQUENTIAL RECORD SELECTION ORDER and RANDOM record selection order.

Sequential record selection order and Random record selection order.

VERIFICATION point ACCESSES the data in the datapool and creates the expected results from the baseline and the active data pool record. Datapool reference resolves and supplies data to verification point. The expected result is compared to the ACTUAL result. The expected and actual results are recorded in the log. Any deviations from the expected results are logged as a FAILURE in the TEST log.

Verification point accesses the data in the datapool and creates the expected results from the baseline and the active data pool record. Datapool reference resolves and supplies data to verification point. The expected result is compared to the actual result. The expected and actual results are recorded in the log. Any deviations from the expected results are logged as a failure in the test log.

Yes. We can replace LITERAL VALUES in existing script with data pool references to add realistic data to the script. We can replace all literal values or just the number or STRING or BOOLEAN literals with a data pool reference. If we do not use an existing datapool variable, then the same literal values are used each TIME we run the script.

Yes. We can replace literal values in existing script with data pool references to add realistic data to the script. We can replace all literal values or just the number or string or Boolean literals with a data pool reference. If we do not use an existing datapool variable, then the same literal values are used each time we run the script.

Once we DATA drive a TEST to CREATE a data pool or create an empty data pool, then we can edit the records and variables in the data pool. We can

• Add – Remove – MOVE - Edit a RECORD and variable
• Edit data pool values
• Cut - Copy or Paste a cell or record or a variable

Once we data drive a test to create a data pool or create an empty data pool, then we can edit the records and variables in the data pool. We can

A data pool is a TEST data set - a collection of related data records which supplies data VALUES to the variables in test script during test script play back. You can create data for a data pool from scratch or we can import existing data into a new data pool from another Functional Tester data pool or from a .csv file.

NOTE: If you need to import the data, you will need to import the data into the same RATIONAL Functional Tester project as the test scripts that access the data. If you need to import data from Test MANAGER data pool, you will need to first associate a RFT project with a Rational project to use the Test Manager data pool.

A data pool is a test data set - a collection of related data records which supplies data values to the variables in test script during test script play back. You can create data for a data pool from scratch or we can import existing data into a new data pool from another Functional Tester data pool or from a .csv file.

Note: If you need to import the data, you will need to import the data into the same Rational Functional Tester project as the test scripts that access the data. If you need to import data from Test Manager data pool, you will need to first associate a RFT project with a Rational project to use the Test Manager data pool.

If the SCRIPTS are recorded in the Java programming language - debugging scripts is the same PROCESS as debugging a Java application. If the scripts are recorded in the VB.NET SCRIPTING - debugging scripts is the same process as debugging a Visual Basic application.

If the scripts are recorded in the Java programming language - debugging scripts is the same process as debugging a Java application. If the scripts are recorded in the VB.NET Scripting - debugging scripts is the same process as debugging a Visual Basic application.

TEST cases should be run to generate test CASE results instead of the script. If we run a script the Test Manager does not generate test case COVERAGE results.

Test cases should be run to generate test case results instead of the script. If we run a script the Test Manager does not generate test case coverage results.

When script runs from RATIONAL Functional Tester, it plays back all recorded ACTIONS. Playback Monitor STARTS and provides information when the script plays back. A log file gets displayed after the script runs completed. When script runs from Test MANAGER, Test Manager creates a temporary suite, runs the suite and removes the suite after the run is completed. We can run a script either from the Test Manager Test Scripts WINDOW or from the Test Manager File menu.

When script runs from Rational Functional Tester, it plays back all recorded actions. Playback Monitor starts and provides information when the script plays back. A log file gets displayed after the script runs completed. When script runs from Test Manager, Test Manager creates a temporary suite, runs the suite and removes the suite after the run is completed. We can run a script either from the Test Manager Test Scripts window or from the Test Manager File menu.

•  MAKE sure that the application under TEST is in the same state that it was in when you record the SCRIPT.
• Ensure that applications and WINDOWS that were open or displayed or active when we started recording the script must be open or displayed or active when we start playback.
• Ensure to restore relevant network settings, active databases and SYSTEM memory (if any) to the same state as when the script was recorded.

• Enabling the WEB browser: Enabling of the browser can be done by clicking on CONFIGURE > "Enable Environments for Testing". This will enable the environments for testing.

• Configuring the HTML applications for testing: It can be done by clicking on Configure > "Configure Applications for Testing" to specify INFORMATION about our application and its environment. For testing MS HTML Applications (MSHTA), we need to run mshta.exe to configure application desired to be tested.

YES. We can do the recording in EXISTING RFT script by bringing our cursor to the desired location & just start the recording. Start the application >> insert verification points >> and ADD all script support functions.

Yes. We can do the recording in existing RFT script by bringing our cursor to the desired location & just start the recording. Start the application >> insert verification points >> and add all script support functions.

In new SCRIPT > RFT includes IMPORT statements for files we need to compile the script and comments containing information of ARCHIVING. Functional Tester uses the script NAME as the class name and sets up testMain. Here, you can add the commands to include in the script.

In new script > RFT includes import statements for files we need to compile the script and comments containing information of archiving. Functional Tester uses the script name as the class name and sets up testMain. Here, you can add the commands to include in the script.

Location where Functional Tester keeps all of the scripts, ALONG with expected and actual results is called as a TEST project. The format of test project is governed by the environment being used. 

Note: If you are using the JAVA LANGUAGE, create a Java test project. However you are using Visual Basic.NET, create a .NET test project.

Location where Functional Tester keeps all of the scripts, along with expected and actual results is called as a test project. The format of test project is governed by the environment being used. 

Note: If you are using the Java language, create a Java test project. However you are using Visual Basic.NET, create a .NET test project.

While recording tests the application can be started by using startApp COMMAND. It makes playing BACK the tests more reliable because startApp uses the application CONFIGURATION information. RFT will open either JAVA applications that we specify or HTML pages in our BROWSER, or run applications in executable form.

While recording tests the application can be started by using startApp command. It makes playing back the tests more reliable because startApp uses the application configuration information. RFT will open either Java applications that we specify or HTML pages in our browser, or run applications in executable form.

• Method of DELETING all cookies for the current PROFILE or USER
• Method of deletes cookies in a specific page or DOMAIN for the current profile or user

Project items like scripts, test object maps, Java files or Visual BASIC files, and datapools can be imported into a Functional Tester project. Functional Tester adds all the project items from the data TRANSFER file into the project SPECIFIED by us. We can use any file COMPRESSION program which support the .zip to view and work with items in the data transfer file. 

Project items like scripts, test object maps, Java files or Visual Basic files, and datapools can be imported into a Functional Tester project. Functional Tester adds all the project items from the data transfer file into the project specified by us. We can use any file compression program which support the .zip to view and work with items in the data transfer file. 

All FUNCTIONAL Tester scripts use default HELPER superclass. These scripts extend the RationalTestScript class and thereby inherit a NUMBER of methods. HOWEVER, advanced users can create their own helper superclass (if they want to add additional methods or OVERRIDE the methods within RationalTestScript).

All Functional Tester scripts use default helper superclass. These scripts extend the RationalTestScript class and thereby inherit a number of methods. However, advanced users can create their own helper superclass (if they want to add additional methods or override the methods within RationalTestScript).

RFT compresses a copy of the files into a data transfer file with the name SPECIFIED by us. It also APPENDS a .rftjdtr (Functional Tester Java Scripting) or .rftvdtr (Functional Tester VB.NET Scripting) extension to it.

RFT compresses a copy of the files into a data transfer file with the name specified by us. It also appends a .rftjdtr (Functional Tester Java Scripting) or .rftvdtr (Functional Tester VB.NET Scripting) extension to it.

Parent-child NESTING and Owner-owned nesting

Parent-child nesting and Owner-owned nesting

Functional Tester runs on the FOLLOWING Host and Test platforms: Windows XP Professional, Windows 2000 Professional & Server, Windows 2000 Server & ADVANCED Server, Windows 2003 Enterprise, Standard & Server

Platforms supporting all functions of RFT EXCEPT the recording: Red Hat LINUX Enterprise WORKSTATION 4.0, SuSE Linux Professional version 9.0, SuSE Linux Enterprise Server 10.0, Novel Desktop 10.0 

Functional Tester runs on the following Host and Test platforms: Windows XP Professional, Windows 2000 Professional & Server, Windows 2000 Server & Advanced Server, Windows 2003 Enterprise, Standard & Server

Platforms supporting all functions of RFT except the recording: Red Hat Linux Enterprise Workstation 4.0, SuSE Linux Professional version 9.0, SuSE Linux Enterprise Server 10.0, Novel Desktop 10.0 

Test playback in RFT is independent of the platform as WELL as independent of browser. E.g. we can record script on Windows and play it back on Linux. Also, the script contains no references to the browser during the recording, we can play back the script using any of the supported VERSIONS of FIREFOX, Mozilla, Internet EXPLORER or Netscape.

Test playback in RFT is independent of the platform as well as independent of browser. E.g. we can record script on Windows and play it back on Linux. Also, the script contains no references to the browser during the recording, we can play back the script using any of the supported versions of Firefox, Mozilla, Internet Explorer or Netscape.

Rational FUNCTIONAL TESTER has two types of VERIFICATION POINTS: Object properties verification point and Data verification points. Data verification point has five further points: MENU hierarchy verification point, Table verification point, Text verification point, Tree hierarchy verification point, List verification point.

Rational Functional Tester has two types of verification points: Object properties verification point and Data verification points. Data verification point has five further points: Menu hierarchy verification point, Table verification point, Text verification point, Tree hierarchy verification point, List verification point.

During the RECORDING verification points can be INSERTED in the script to confirm the state of an object in the application.

A verification point captures the object information based UPON the type of verification point and stores it in a BASELINE data file. The information in the BASE file becomes baseline of expected state of object during subsequent builds. 

During the recording verification points can be inserted in the script to confirm the state of an object in the application.

A verification point captures the object information based upon the type of verification point and stores it in a baseline data file. The information in the base file becomes baseline of expected state of object during subsequent builds. 

We can export PROJECT ITEMS like scripts, TEST object maps, Java files, Visual Basic files and data pools to another Functional Tester project. When we export a script Functional Tester includes all necessary files like shared test object maps EVEN THOUGH it was not selected by us.

We can export project items like scripts, test object maps, Java files, Visual Basic files and data pools to another Functional Tester project. When we export a script Functional Tester includes all necessary files like shared test object maps even though it was not selected by us.

• CONNECT to Functional Test Project: It allows us to connect to an EXISTING Functional Tester project.
• Refresh Projects: It enables us to REPAINT the DISPLAY to reflect changes.
• Synchronize with Editor: It scrolls in the tree HIERARCHY to the name of the script currently displayed in the Java Editor.

Yes. We can not play back Functional Tester script or test cases or SUITES that include Functional Tester scripts in DISASSOCIATED project from TestManager. Test Manager deletes test script source from the disassociated project. This operation can not be undo. If we ASSOCIATE Functional Test project with Rational project again, TestManager creates NEW test script source.

Yes. We can not play back Functional Tester script or test cases or suites that include Functional Tester scripts in disassociated project from TestManager. Test Manager deletes test script source from the disassociated project. This operation can not be undo. If we associate Functional Test project with Rational project again, TestManager creates new test script source.

1. Management of testing ASSETS from one Rational project.
2. You can RECORD and play BACK all Functional TESTER scripts from Rational TestManager. 
3. Playing back Functional Tester script on different computer using Rational Test Agents through TestManager.
4. Management Functional Tester logs using the Test LOG window of TestManager.
5. Use of Test Manager reports to get information about the results of running Functional Tester test script and get coverage report for testing project.
6. Use TestManager suite to coordinate the way that scripts run. 

1. Creating and playingback the scripts from within RATIONAL TestManager.
2. Using the TestManager Agent for PLAYING back scripts on remote computer.
3. You can VIEW the scripts from the Test Scripts WINDOW of Rational TestManager.

RATIONAL Test PROJECT is used for storing test assets like test PLANS test cases, test logs, reports, builds etc. To associate a Functional Tester project with a Rational project, a Rational project NEEDS to be created to store the test assets. Functional Test project stores all application test assets like scripts, object maps, verification point baseline files and script templates. Functional Test project is created before recording the scripts.

Rational Test project is used for storing test assets like test plans test cases, test logs, reports, builds etc. To associate a Functional Tester project with a Rational project, a Rational project needs to be created to store the test assets. Functional Test project stores all application test assets like scripts, object maps, verification point baseline files and script templates. Functional Test project is created before recording the scripts.

TestManager: It includes the Test Manager Log, running Windows & Linux remote playback agents and test management features LIKE running scripts as part of a test suite. FUNCTIONAL Tester has its own logs and does not depend on the TestManager log INTEGRATION.

ClearQuest Test Manager: It helps us in associating functional test scripts to Test Cases and executes them. USING CQTM we can ANALYZE the received execution results and record those results for reporting and analysis.

TestManager: It includes the Test Manager Log, running Windows & Linux remote playback agents and test management features like running scripts as part of a test suite. Functional Tester has its own logs and does not depend on the TestManager log integration.

ClearQuest Test Manager: It helps us in associating functional test scripts to Test Cases and executes them. Using CQTM we can analyze the received execution results and record those results for reporting and analysis.

First Way: We can record a script on Windows Environment and export it to Linux & then play it back on Linux.

Second Way: By writing scripts USING the Test Object Insert TOOL. Instead of creating an object map through recording we populate it OUTSIDE of the recorder by opening the map and selecting OBJECTS in the test application.

We can insert verification points without recording, by opening the Verification Point wizard from the Script Explorer.

First Way: We can record a script on Windows Environment and export it to Linux & then play it back on Linux.

Second Way: By writing scripts using the Test Object Insert tool. Instead of creating an object map through recording we populate it outside of the recorder by opening the map and selecting objects in the test application.

We can insert verification points without recording, by opening the Verification Point wizard from the Script Explorer.