IBM RFT Interview Questions: Q. 51 to 60
Q. 51: How do we test our software applications by running the scripts in RFT?
When we play back a script, RFT replays all the recorded actions, which automates the software testing cycle.
Such automation allows us to test each new build of our application faster and more thoroughly compared to manual testing, thereby reducing the testing time and increasing the coverage and overall consistency.
<<<<<< =================== >>>>>>
Q. 52: What are the general phases of script playback?
There are two general phases of script playback:
1) Test Development Phase: Here we play back scripts to verify that they work as intended, using the same version of the application-under-test that we used to record. This phase validates
the expected behavior for the application.
2) Regression Testing Phase: Here we play back scripts to compare the latest build of the application to the baseline established during the test development phase. Regression testing identifies differences that may have been introduced since the last build. We can evaluate these differences to determine whether they are defects or changes.
<<<<<< =================== >>>>>>
Q. 53: What are the steps involved in test development phase using RFT?
The test development phase consists of following six steps:
1) Restore the test environment and set the playback options.
2) Play back each script against the same version of the application-under-test that was used for recording to verify that the script performs as intended.
3) Analyze the results in the RFT log. If we associate a Functional Tester project with the current Rational project, we can analyze the results using the Test Log window of TestManager.
4) Use the Functional Tester Verification Point Comparator to determine the cause of verification point failures.
5) If the script fails, edit, debug, or re-record it so that it runs as required.
6) If we associate a Functional Tester project with the current Rational project, we can group individual scripts into a test suite. Play back the suite to verify that the scripts work properly. If necessary, edit, debug, or re-record the scripts.
<<<<<< =================== >>>>>>
Q. 54: What are the steps involved in regression testing phase using RFT?
The regression-testing phase consists of following five steps:
1) Restore the testing environment and set the playback options.
2) Play back the test script against a new build of the application-under-test.
3) Analyze the results in the Functional Tester log. If we associate a Functional Tester project with the current Rational� project, we can analyze the results using the Test Log window of TestManager.
4) Use the Functional Tester Verification Point Comparator to determine the cause of verification point failures. If verification points fail because of intentional changes to the application-under-test, update the baseline data using the Comparator.
5) If necessary, revise your test scripts to use new features in the application under test. Then play back the revised test scripts against the current build and reevaluate the results.
<<<<<< =================== >>>>>>
Q. 55: What is the purpose of Playback Monitor in RFT?
When we do the playback of our script, we can view the script name, the number of the line that is executing, status icons, and a description of the action in progress from the Playback Monitor.
The Playback Monitor consists of following four parts:
1) Script name
2) Description of action in progress
3) Status icons
4) Script line number
5) Stop and pause or resume buttons
<<<<<< =================== >>>>>>
Q. 56: What are Local and agent computers in RFT?
When we associate a Functional Tester project with a Rational project, we can use TestManager to run the Functional Tester scripts on computers that are designated as Agent computers from a single Windows computer, called the Local computer.
<<<<<< =================== >>>>>>
Q. 57: What are the actions performed by the agent computers while using RFT?
Agent computers are used to perform following tasks:
1) Running the scripts on more than one computer. If we are running a test, we can save time by running the scripts on the next available Agent computer instead of running all scripts on the Local computer.
2) Test different machine configurations. If we are testing various hardware and software configurations, we can run scripts on Agent computers that are set up with different configurations.
3) Run Functional Tester scripts remotely on Linux or Windows computers. If we run Functional Tester scripts remotely, we must enable environments and configure applications on the Linux or Windows Agent computers.
<<<<<< =================== >>>>>>
Q. 58: What are the actions required to run a RFT script from TestManager?
To run a RFT script from TestManager we need to do the following:
1) In Functional Tester- Java Scripting, associate a Functional Tester project with a Rational project.
2) In Functional Tester- VB.NET Scripting, associate a Functional Tester project with a Rational project.
3) On a remote computer, we need to install the Rational Test Agent software on the Agent computer and start the agent.
4) If we need an external library to run a script, for example a .jar or .dll file, we need to install the software on the system on which we plan to run the script.
5) To install a .dll, add the library to a directory that is in system search paths.
6) To install a .jar file, add it to the Functional Tester customization directory. Functional Tester adds all .jar files in the customization directory to the script classpath. The default location for the customization directory is: C:Documents and SettingsAll UsersApplication DataIBMRFTcustomization
<<<<<< =================== >>>>>>
Q. 59: What is the purpose of using ScriptAssure in RFT?
With the help of ScriptAssure feature we can play back the scripts successfully even when the application under test has been updated.
For RFT to recognize an object in the application under test, the object properties must match the properties recorded in the test object map. By default, RFT can find the object if one or two properties do not match. If two properties do not match, RFT writes a weak recognition warning to the log. If more than three properties do not match, RFT cannot find the object in the application.
Thus even if some objects in the application under test have changed, we can still play back scripts in RFT by using the ScriptAssure feature to control object-matching sensitivity.
<<<<<< =================== >>>>>>
Q. 60: What are the ways of using ScriptAssure in RFT?
ScriptAssure feature can be used in following two ways:
1) Standard way: The ScriptAssure Page-Standard controls object-matching sensitivity during playback by using a slider control. To set the tolerance for differences between the object in the application-under-test, we move the Recognition Level slider between Strict and Tolerant. To find differences between the object and the recognition properties, we move the Warning Level slider between High and None.
2) Advanced way: The ScriptAssure Page-Advanced sets thresholds for recognition scores. We can set a maximum score to consider a test object as a candidate for recognition; we can also request warnings when candidate objects have a score higher than the designated threshold.
Continue to Next Part : Q 61 to 70
An expert on R&D, Online Training and Publishing. He is M.Tech. (Honours) and is a part of the STG team since inception.