IBM RFT Interview Questions: Q. 121 to 130
Q. 121: What are Globalized applications?
Globalized applications are those in which all of the strings like messages, labels, and text, are localized, that is, translated to the language of the location from which it was started or launched.
For example, if an application is started from a Japanese locale or operating system, then all of the information will appear in Japanese. Similarly, if an application is started from a French locale or operating system, the Information will appear in French, and so on.
“Globalized” also refers to applications that allow input and output of a non-English character set.
<<<<<< =================== >>>>>>
Q. 122: What are the problems faced while automating the globalized applications?
1) Automated scripts recorded for a particular locale
fails when played back in a different locale. This happens because the object definition used for playing back the automation script (for instance, the label of the button on which the automation script has to operate) may be different from an English to a Japanese locale.2) Verification points checked in a particular locale fail when we attempt to affirm them in a different locale. This happens because the expected or initially recorded value of the verification point does not match the actual value displayed in the globalized application under test, because it was launched from a different location.
3) Data-driven test scripts do not pick and populate the data set, depending on the location from which the application under test was launched. This happens because there is no implicit intelligence built into the automation script to help determine the language.
<<<<<< =================== >>>>>>
Q. 123: What are the various constituents of architecture of QSE Framework for RFT?
Architecture of IBM QSE Framework for RFT consists of three tiers:
1) “Appobject” classes which logically group GUI elements together. These classes consist of discrete, granular private object maps that contain a small number of related GUI elements, along with routines that provide access to these elements.
2) Tasks or methods, which execute commonly – traveled paths through the GUI.
3) Test cases that invoke the tasks, verify the state of the application, and log the results.
This architecture consists of a framework consisting of three folders which are a package within an RFT project, and represents one tier of the three-tiered architecture :
a) Appobjects Folder
b) Tasks Folder
c) Testcases Folder
<<<<<< =================== >>>>>>
Q. 124: What is the process of creating verification point in RFT?
Process of creating verification point in RFT follows following four steps.
Step – 1: Select an object
Step – 2: Perform an action
Step – 3: Provide variable name
Step – 4: Specify verification point data
Within verification point data, we can specify what we want to test. For example, For an object we can have verification point on its properties orfor a menu we can have verification point for data in the menu.
<<<<<< =================== >>>>>>
Q. 125: How do we represent a global view of the software under test in RFT?
RFT uses an object called the “RootTestObject” to represent a global view of the software under test.
1) If we want to search the entire application, we use the find method on the RootTestObject.
2) If we want to search a specific object, then use find on that TestObject. Searching a specific “TestObject” will search only the children of that TestObject
<<<<<< =================== >>>>>>
Q. 126: How can a beginner effectively use RFT?
Before understanding how to effectively use the RFT as an automation tool, we must have fair understanding of the following:
1) Objects and properties
2) Common problems with browsers
3) Verification points
4) Low-level commands
5) The script helper superclass
<<<<<< =================== >>>>>>
Q. 127: What are the objects & their properties when we talk in relation to RFT?
Components like the dialog boxes, command buttons or labels have some sort of information attached to them, which is known as their property. Properties of the objects have a name and some value.
While undertaking any testing project, we usually need various properties of the objects under the test process so that we can perform some sort of verification so that we can programmatically find out the next action expected from the test script.
<<<<<< =================== >>>>>>
Q. 128: Why do we normally use object properties during the test?
We usually come across a need like the following when we need to access the properties of a test object:
1) To draw a comparison among previous versions of a property value to its current value dynamically at runtime
2) To add a branch in the RFT script which is based on the current value of a property contained in an object
<<<<<< =================== >>>>>>
Q. 129: How can we retrieve the value of an object property programmatically?
We can retrieve the value of an object’s property by
1) Getting object’s property programmatically by using the “getProperty” method.
2) Viewing the object properties by temporarily recording an Object Properties verification point for that object.
3) Inserting the commands to extract a property value from an object into a variable through the VP and Actions wizard.
4) By using “setProperty method”. However, RFT provides this method with a disclaimer: “Do not use it unless you are sure of the result”. Reason being this method calls internal methods which may violate the integrity of the application being tested.
<<<<<< =================== >>>>>>
Q. 130: What is the significance of TestObjects in RFT?
A “TestObject” represents a connection point between the script which is played back and the application being tested.
For every “TestObject” in a created test script, a corresponding object resides in the application which had been recorded by us for a particular application. This object is now available in the Test Object Map as well.
Continue to Next Part : Q 131 to 140
An expert on R&D, Online Training and Publishing. He is M.Tech. (Honours) and is a part of the STG team since inception.