Win Runner Interview Questions and Answers
Question - 41 : - Specify a command which can show us the information from the status bar?
Answer - 41 : -
statusbar_get_text (”Status Bar”, O, statustext);
Here the variable status text contains information in the status bar.
Question - 42 : - Is there any way to face unexpected errors in WinRunner?
Answer - 42 : -
WinRunner provides exception handling to face and detect and unexpected events and to take action accordingly. WinRunner supports the following types of exceptions.
- Pop-up Exceptions: to discover and support the appearance of a window
- Object Exceptions: to discover and manage any changes in the property of a GUI Object
- TSL Exceptions: to discover and manage TSL functions returning specific error codes.
- Web Exceptions: to discover and manage any errors in the website, in case web test add-in is loaded in the application
- UAE Exceptions: to manage exceptions divided by zero or null pointers.
Question - 43 : - How to freeze GUI Spy?
Answer - 43 : -
Press “Ctrl+F3” to freeze GUI Spy.
Question - 44 : - Define Data Parameterization in WinRunner
Answer - 44 : -
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 script sizes can also be reduced. This process is widely used when values change after each and every test execution. For example, testing the sales order application where the order number is incremented by 1. Data parameterization is the best suit for this type of application
Question - 45 : - What do you know about the WinRunner testing tool?
Answer - 45 : -
Ans: WinRunner is a popular automated graphical user interface testing tool that allows users to record and script the user interface test cases. The main purpose of using the WinRunner testing tool is used to capture, verify, and replay the user interface testing scripts. This tool works well with HP Quick test professionals and supports enterprise-level quality assurance capabilities. The Win Runner is developed by HP Company.
Question - 46 : - Name the different testing stages used in Win Runner?
Answer - 46 : -
Below are the 6 testing stages used in Win Runner;
- Create GUI map: this map file used to identify graphical user interface objects used in many application developments that you need to be tested.
- Testing can be performed by using these stages:
a. Recording
b. Programming and
c. Combining both.
- Debug mode is used by testing professionals to provide consistency, monitoring, and also offers to break points in test cases.
- Run test case mode used to test the application and compare the data application to capture the data sets.
- View result stage gives the status of any test – PASS or FAIL
- Report detect mode is used to identify failed test cases which are reported from the result window system.
Answer - 47 : -
Below is the language used in WinRunner;
TSL -> Test scripting language, this is similar to the C programming language.
Question - 48 : - Brief about the test scripts you have created in WinRunner?
Answer - 48 : - WinRunner test script consists of Mercury’s Interactive test script language or TSL. With the help of this, we can modify the test records which are recorded. This process can be done by adding programming elements and TSL functionalities or function generator. As we already know that WinRunner is a visual programming tool.
Question - 49 : - Explain the different types of modes in which we can run test scripts in WinRunner?
Answer - 49 : -
There are three different test modes used in WinRunner;
1. Verify -> this testing mode is used to check the various applications and compare that with already existing data.
2. Debug -> this testing mode helps users to find different bugs to run test scripts.
3. Update -> this testing mode helps the user to modify the test results or generate a new result expected folder.
Question - 50 : - Explain WinRunner’s evaluation of test results?
Answer - 50 : - WinRunner usually displays the test results in the Report folder. This report makes a list of all the events during the time of the test case running like checkpoints, error messages, user and system messages. If you found any type of mismatch at the check point level, you need to compare the actual or expected results in the Test Results Window.