If you're looking for WinRunner Interview Questions for Experienced or Freshers, you are at right place. There are lot of opportunities from many reputed companies in the world. According to research HP Winrunner has a market share of about 3.3%. So, You still have opportunity to move ahead in your career in Testing Analyst. Mindmajix offers Advanced WinRunner Interview Questions 2019 that helps you in cracking your interview & acquire dream career as Quality Assurance Analyst Developer.
Q1) What is WinRunner?
WinRunner, developed by HP, is a functional and automated GUI testing tool. Using this tool, user can record UI interactions and can replay them as well as test scripts. It is widely used to identify any defects in business processes.
Q2) Please describe WinRunner testing stages.
There are main 6 stages involved in WinRunner testing process.
1. Creating a GUI Map file can help WinRunner to identify GUI objects used in the application for which one wants to test
2. Tests can be generated by
3. Running test cases in debug mode can help us to ensure consistency in tests run. Breakpoints in tests, variables monitoring and ease of control on test run can make work easy of finding defects.
4. Running test cases in verify mode test the application and compares the data of application with the earlier captured data.
5. This stage states the status of any test – PASS or FAIL.
6. In case of any failure of any test case due to some defect, that defect can be directly reported from the Test Results window.
Q3) Specify the language used in WinRunner.
WinRunner used TSL-Test Script Language. It is similar to C.
Q4) Brief about the test scripts you’ve created in WinRunner.
WinRunner test scripts contain statements written in Mercury Interactive’s Test Script Language (TSL). We can modify the recorded test scripts, either by adding more programming elements and TSL functions or by using Function Generator, a WinRunner’s visual programming tool.
Q5) Explain WinRunner’s Evaluation of Test Results.
WinRunner displays test results in a report. This report lists out all the events took place during the test run like error messages, checkpoints, user messages or system messages. In case of any mismatch at checkpoint, we can compare the expected and actual results in Test Results Window.
Q6) Explain different types of modes in which we can run test scripts in WinRunner.
WinRunner enables us to run test scripts in three different modes as per the phase of the testing.
1. Verify: this mode helps us to check the application and compare it with earlier captured data.
2. Debug: this mode helps us to find bugs in a test script.
3. Update: this mode helps us to modify the expected results or generate a new expected results folder.
Q7) What’s there in Wrun.ini File?
Wrun.ini file is setup configuration file for WinRunner.
Q8) Explain the use of set_window command
Set_window command is used to set the focus on any window. This command is used to place focus on specified window before implementing any test scripts.
set_window (, )
Q9) Describe few scenarios where WinRunner cannot identify GUI Objects.
There can be few cases where WinRunner won’t be able to identify GUI objects.
Q10) What does it mean by logical name of any object?
Logical name of any object is nothing but the text label of that object. This makes the code easily understandable and readable.
Q11) Differentiate between GUI Map and GUI Map Files.
GUI Map file is a file containing all GUI objects used in application with its logical names and physical description.
GUI Map is a collection of all GUI Map files.
Q12) How to organize GUI Map files?
We can organize GUI Map files in 2 ways
1. Global GUI Map File: there is only one GUI Map file for the whole application
2. GUI Map File per test: For every test, a separate GUI Map file will be created by WinRunner
Q13) How can we load GUI Map?
We can load GUI Map by using the command GUI_load ().
Q14) Can we unload GUI Map file? If yes, How?
Yes, it is possible to unload GUI Map file.
To unload any particular GUI Map files:
GUI_close () or GUI_unload ()
To unload all GUI Map files:
GUI_close_all or GUI_unload_all
Q15) What is GUI Spy?
GUI Spy enables us to view all the properties of any GUI object. As soon as the spy pointer points to any object, GUI Spy displays all the properties and values related to that object in GUI Spy dialog box. However we can filter to see all or selected set of properties in dialog box.
Q16) Tell me the extension of GUI Map file.
GUI Map File’s extension is - “.gui”.
Q17) Is it possible to edit logical name of any object? If yes, then How?
Logical names are generally given by WinRunner. They are usually text labels of that object. But if one wishes to change the logical name of any object, then yes it is possible to do so by using GUI Map editor.
Q18) Explain different Recording modes.
WinRunner provides two ways of recording.
1. Context Sensitive Recording: In this type of recording, all the interactions performed by GUI objects in application are recorded.
2. Analog Recording: In this type of recording, mouse clicks, keyboard inputs and the x,y coordinates traversed by mouse in screen is recorded.
Q19) In case of missing object label, what can be logical name of that GUI object
If object doesn’t have any label/text, then attached text would be the logical name of that object.
Q20) Specify drawbacks of loading GUI Map file using Start up scripts.
Below are the drawbacks of loading GUI Map file using start up scripts.
Q21) Describe the objective of Temp GUI Map File.
When we run any test scripts in WinRunner, WinRunner identifies windows and objects by itself and also load them into a temporary GUI Map file. We have an option to load this temporary GUI Map File while running any tests.
Q22) Give an overview about Checkpoints in WinRunner
Checkpoint is the place where we can compare and check actual and expected results of any tests. There are four types of checkpoints in WinRunner.
1. GUI Checkpoints: to check and ensure details about GUI objects. For example, which item is crossed or button is enabled
2. Text Checkpoints: to verify GUI objects contents
3. Database Checkpoints: to check the data set
4. Bitmap Checkpoints: to compare a snapshot to earlier version of same test.
Q23) Specify the command used to find resolution settings.
Q24) Where can we use regexp_label Property and regexp_msw_class?
1. The regexp_label property: It is only applicable to windows. It privately places a regular expression into a window’s label description.
2. The regexp_msw_class property: It is mandatory for all windows and object class objects. It places a regular expression into an object’s MSW_class.
These both properties are used to handle constantly changing windows’ labels.
Q25) Mention drawbacks of Compile Module.
Running Compile Module in WinRunner has few drawbacks as mentioned below.
1. Checkpoints can’t be inserted in Compile Module
2. Sync Points also can’t be placed
3. It is non executable.
Q26) Define Boundary test.
Boundary test is termed as a test carried to ensure program’s responses to extreme inputs. It ensures that program can handles extreme inputs and produce respective outputs at both boundaries.
Q27) Specify command which can show us the information from status bar?
statusbar_get_text (”Status Bar”, O, statustext);
Here the variable statustext contains information in status bar.
Q28) Is there any way to face unexpected errors in WinRunner?
WinRunner provides exception handling to face and detect and unexpected event and to take action accordingly. WinRunner supports following types of exceptions.
1. Pop-up Exceptions: to discover and support the appearance of a window
2. Object Exceptions: to discover and manage any changes in property of a GUI Object
3. TSL Exceptions: to discover and manage TSL functions returning specific error codes.
4. Web Exceptions: to discover and manage any errors in website, in case webtest add-in is loaded in application
5. UAE Exceptions: to manage exceptions like divided by zero or null pointers.
Q29) How to freeze GUI Spy?
Press “Ctrl+F3” to freeze GUI Spy.
Q30) Define Data Parameterization in WinRunner
Data Parameterization is a process where data is recorded multiple times and WinRunner has a Data is written multiple times, while WinRunner has an iterative loop to execute those data. Due to the loop, test scripts sizes can also be reduced. This process is widely used when values changes after each and every test execution. For example, testing the sales order application where order number is incremented by 1. Data parameterization is best suit for this type of application
Free Demo for Corporate & Online Trainings.