• +91 9971497814
  • info@interviewmaterial.com

Win Runner Interview Questions Answers

Question 1 : Have you created test scripts and what is contained in the test scripts?

Answer 1 : Yes I have created test scripts. It contains the statement in Mercury Interactive’s Test Script Language (TSL). These statements appear as a test script in a test window. You can then enhance your recorded test script, either by typing in additional TSL functions and programming elements or by using WinRunner’s visual programming tool, the Function Generator.

Question 2 : Have you integrated your automated scripts from TestDirector?

Answer 2 : When you work with WinRunner, you can choose to save your tests directly to your TestDirector database or while creating a test case in the TestDirector we can specify whether the script in automated or manual. And if it is automated script then TestDirector will build a skeleton for the script that can be later modified into one which could be used to test the AUT.

Question 3 : Have you performed debugging of the scripts?

Answer 3 : Yes, I have performed debugging of scripts. We can debug the script by executing the script in the debug mode. We can also debug script using the Step, Step Into, Step out functionalities provided by the WinRunner.

Question 4 : How do you view the contents of the GUI map?

Answer 4 : GUI Map editor displays the content of a GUI Map. We can invoke GUI Map Editor from the Tools Menu in WinRunner. The GUI Map Editor displays the various GUI Map files created and the windows and objects learned in to them with their logical name and physical description.

Question 5 : How does WinRunner evaluate test results?

Answer 5 : Following each test run, WinRunner displays the results in a report. The report details all the major events that occurred during the run, such as checkpoints, error messages, system messages, or user messages. If mismatches are detected at checkpoints during the test run, you can view the expected results and the actual results from the Test Results window.

Question 6 : If the object does not have a name then what will be the logical name?

Answer 6 : If the object does not have a name then the logical name could be the attached text.

Question 7 : What are the different modes of recording?

Answer 7 : There are two type of recording in WinRunner. Context Sensitive recording records the operations you perform on your application by identifying Graphical User Interface (GUI) objects. Analog recording records keyboard input, mouse clicks, and the precise x- and y-coordinates traveled by the mouse pointer across the screen.

Question 8 : What are the reasons that WinRunner fails to identify an object on the GUI?

Answer 8 : WinRunner fails to identify an object in a GUI due to various reasons. The object is not a standard windows object. If the browser used is not compatible with the WinRunner version, GUI Map Editor will not be able to learn any of the objects displayed in the browser window.

Question 9 : What is meant by the logical name of the object?

Answer 9 : An object’s logical name is determined by its class. In most cases, the logical name is the label that appears on an object.

Question 10 : What is the different between GUI map and GUI map files?

Answer 10 : The GUI map is actually the sum of one or more GUI map files. There are two modes for organizing GUI map files. Global GUI Map file: a single GUI Map file for the entire application. GUI Map File per Test: WinRunner automatically creates a GUI Map file for each test created. GUI Map file is a file which contains the windows and the objects learned by the WinRunner with its logical name and their physical description.

Win Runner Contributors


Share your email for latest updates


Our partners