Win Runner Interview Questions and Answers
Question - 51 : - Explain the use of the set_window command?
Answer - 51 : -
Set_window command is mainly used to focus on any window systems. This command is also used to place your focus on the detected windows before performing test script implementation.
The syntax is as follows;
Set_window (,).
Question - 52 : - Describe any two scenarios where WinRunner cannot identify GUI objects?
Answer - 52 : -
The following are the two scenarios which I would like to mention them;
1. If you are using an object which is not a standard window object, by that time you should utilize the WinRunner.
2. If any browser which you are using is not supported by the WinRunner version.
Question - 53 : - How can you unload GUI map files in WinRunner?
Answer - 53 : -
Steps involved in unloading the GUI map files;
1. To unload any GUI map file (any particular file) use the following methods;
GUI_Close () or GUI _Unload ().
2. To unload all the GUI map files you have to use the methods;
GUI_Close_all or GUI_Unload_all.
Question - 54 : - Explain two different types of recording modes?
Answer - 54 : -
WinRunner uses the two types of recording modes;
1. Context sensitive recording: in this type of recording in WinRunner, all the required interactions will be performed by the graphical user interface object in the application are recorded.
2. Analog Recording: in this type of recording in WinRunner, the components which we are using included are mouse clicks, X or Y coordinates, and Keyboard inputs will be recorded.
Question - 55 : - Give an overview of checkpoints in WinRunner?
Answer - 55 : -
Check point is the place, where need to compare and check the actual and expected data results of any tests. There are four types of checkpoints in WinRunner,
- GUI checkpoints: To check and ensure details regarding GUI objects. For instance, the item is crossed or the object button is enabled.
- Text checkpoints: This checkpoint is used to verify Graphical user interface objects contents.
- Database checkpoints: this check point is used to check the data set.
- Bitmap checkpoints: this checkpoint is used to compare any snapshot to set an earlier version of the WinRunner.
How to perform debugging of the scripts?
Answer - 56 : -
Debugging of the test script can be performed in following steps:
1) To enable the script debugger, choose TOOL menus and select Script Debugger.
2) Run the test script
3) Choose from the following option:
A. Step over: execute the script one at a time.
B. Step In: execute the script one at a time.
C. Step Out:
D. Set next step:
E. Run/pause
F. Halt script:
G. Set/clear break point.
H. Edit script
I. Open close data viewer.
J. Authenticate / Deauthenticate Script.
4) Select Pause on error if you want scripts to pause when errors are encountered.
Question - 57 : - How does WinRunner recognize objects on the application?
Answer - 57 : -
WinRunner identifies the object on the identification properties of the object saved in the GUI Map file. These properties are:
Physical name: like “save” for a save dialog box, or “OK” for an OK button
Logical name: is the name given by WinRunner when adding an object into the repository. In most of the cases WinRunner takes the text which is attached with the object, work as the Logical name.
GUI Map contains the logical name and a physical description in respect to the each object in the application. WinRunner checks that there are no other objects in the GUI map with the same name.
Question - 58 : - How do you analyze results and report the defects?
Answer - 58 : -
After execution of test script WinRunner automatically generate the results in a report. The report summarizes all tasks which occurred during the execution of test script, like checkpoints, error messages. Tester read the reports and results to evaluate whether the expected results and actual results are matching or not. In case both are not matching then this is treated as a bug and this is locked in the bug report. This bug report can be send to the development team direct from the WinRunner interface by integrating mail option with the WinRunner.
Question - 59 : - What is logical name in WinRunner?
Answer - 59 : -
Logical name: is the name given by WinRunner when adding an object into the repository. Generally, the logical name can be the label that is displayed on object of the application. WinRunner ensure that there are no other objects with the same logical name in the GUI map.
Question - 60 : - What is the purpose of loading WinRunner Add-Ins?
Answer - 60 : -
Add-Ins: are small programs or files which can be added to computer in order to enhance the capabilities of the system. The purposes of loading Add-Ins into WinRunner are following:
- To increase capabilities of the system.
- To improve the graphics quality, communications interface.
- To load the particular function into the memory.
- To excess only those function which are required for the execution of the script.