Detailed Analysis of WinRunner Automation Tool with Regularly Posed Queries and Responses for the Impending Interview Preparation.
This article is part of the series “WinRunner Interview Query and Response Compilation”.
Recommended IPTV Service Providers
- IPTVGREAT – Rating 4.8/5 ( 600+ Reviews )
- IPTVRESALE – Rating 5/5 ( 200+ Reviews )
- IPTVGANG – Rating 4.7/5 ( 1200+ Reviews )
- IPTVUNLOCK – Rating 5/5 ( 65 Reviews )
- IPTVFOLLOW -Rating 5/5 ( 48 Reviews )
- IPTVTOPS – Rating 5/5 ( 43 Reviews )
The WinRunner Automation Tool is a product of Mercury Interactive, which was later acquired by HP. Post-acquisition, HP discontinued support for WinRunner and advised users to switch to HP Functional Testing software.
Presented below are essential WinRunner interview questions often put up during the Automation Testing interview. In case of any doubts or queries, please feel free to engage us in the comments section.
Our WinRunner tutorial postings form a fragment of the Testing Interview readying series aimed at aiding your preparation.
Learning Outcomes:
Preparation for WinRunner Automation Tool
Listed below are several questions and responses to aid WinRunner Automation tool exercise.
Q #1) What is the procedure to examine Test results in WinRunner software and report any flaws?
Response: Upon conclusion of a test in WinRunner, the results are exhibited in a report format.
The report records everyday information about the test execution i.e. date, mode of operation, and overall runtime. Furthermore, the report comprises all the significant occurrences during the run, like checkpoints, system messages, error messages, or user messages.
Any discrepancies can be spotted in the report panel by juxtaposing the Expected outcome and the Actual outcome. Should the test execution fail due to a bug in the application being tested, one can report information about the flaw directly from the Test Results window.
This information is subsequently relayed via email to the Quality Assurance Manager, who monitors the bug until it’s fixed.
Q #2) What is the functionality provided by the Test Director Testing Tool?
Response: Test Director is a software Test Management Tool developed by Mercury Interactive. It aids Quality Assurance personnel in managing and structuring the testing process.
With TestDirector, you can establish a database of manual and automated tests, construct test cycles, execute tests, and report and track defects. You can also create reports and graphs to aid reviewing the progress of planning tests, executing tests, and tracking defects prior to a software release.
Q #3) How can one integrate Automated Scripts from TestDirector into WinRunner Scripts?
Response: When using WinRunner to generate any test script, you are given the opportunity to save it directly to the Test Director test repository.
Alternatively, while creating a test case in TestDirector, we are asked to specify whether it’s an automated or manual script.
If it’s an automated script, then TestDirector will design a skeleton for the script like TSL (Test Script Language) of WinRunner that can be subsequently modified into one that can be used to test the application.
Q #4) What are the different manners of Recording in WinRunner?
Answer: There are two methods of Recording in WinRunner:
- Context-Sensitive Recording, which logs the operations conducted on the application by identifying Graphical User Interface (GUI) objects. WinRunner identifies all the objects in the window that are clicked on, such as lists, windows, menus, buttons, and the type of operation performed such as move, select, enable, etc.
- Analog Recording logs keyboard input, mouse clicks, and the precise x- and y-coordinates traversed by the mouse pointer across the screen i.e WinRunner records the exact co-ordinates traversed by the mouse.
Q #5) What is the objective of loading WinRunner Add-Ins?
Response: Add-Ins are utilized in WinRunner to load functions specific to a particular add-in into the memory. While scripting, only those functions in the add-in that are chosen will be displayed in the function generator.
While executing the script only those functions that are in the loaded add-in will be implemented, otherwise, WinRunner will generate an error message stating it doesn’t recognize the function.
Q #6) What are the causes that result in WinRunner’s failure to identify the GUI object?
Response: WinRunner may fail to identify an object in a GUI for several reasons. Here are a few reasons.
- The object is not a standard windows object.
- If the browser being used is not compatible with the WinRunner version, then the GUI Map Editor will fail to learn any of the objects displayed in the browser window.
Q #7) What inference can be drawn from the Logical name of the object?
Response: When an object is clicked, WinRunner assigns a Logical name to the object, which is generally the object’s text label. Logical names simplify reading the test script.
For example, when you have clicked the Order No. checkbox, WinRunner has recorded the following statement in WinRunner TSL:
button_set (“Order No.”, ON);
“Order No.” is the logical name of the object.
The Logical name of an object is determined by its class. Most often, the logical name is the label that appears on an object.
Q #8) What would be the Logical name if the object does not have a name?
Response: If the object doesn’t possess a name then the logical name may be the attached text.
Q #9) What differentiates GUI map and GUI map files?
Response: The GUI map is the aggregation of multiple GUI map files. GUI map files can be organized in two modes.
- Global GUI Map file: A single GUI Map file for the entire application.
- GUI Map File per Test: WinRunner automatically generates a GUI Map file for each test created.
GUI Map file is a file comprising windows and objects learned by WinRunner along with their logical name and physical description.
WinRunner Interview Queries with Responses
This tutorial on the WinRunner interview preparation series will provide the frequently posed WinRunner interview queries with their corresponding responses.
Majority of the queries center around Test Script Language (TSL), recording scripts in WinRunner, and introduction to some crucial and widely used WinRunner commands.
Q #1) What function does the set_window command serve?
Response: Set_Window command refocuses the required window. This command is exercised to focus the required window before executing tests on a specific window.
Syntax: set_window(
In this