WinRunner Interview Questions and Answers

WinRunner Interview Questions and Answers from Codingcompiler – In this article we have prepared the most frequently asked WinRunner Interview Questions and Answers for beginners and experienced by covering all the core areas by professionals.

WinRunner Interview Questions

  1. What is Winrunner?
  2. What is the purpose of set_window command?
  3. How many types of Run Modes are available in WinRunner?
  4. How WinRunner identifies GUI objects in an application?
  5. Please describe WinRunner testing stages
  6. What In Contained In The Gui Map?
  7. How Does Winrunner Evaluates Test Results?
  8. What’s the Verify Mode?
  9. What’s the Debug Mode?
  10. What is the Use of Test Director Testing Tool?

WinRunner Interview Questions and Answers

Q1).What is Winrunner?

Ans: HP WinRunner software was an automated functional GUI testing tool that allowed a user to record and play back user interface (UI) interactions as test scripts. As a functional test suite, it worked with HP QuickTest Professional and supported enterprise quality assurance.

It captured, verified and replayed user interactions automatically, in order to identify defects and determine whether business processes worked as designed.

Q2).What is the purpose of set_window command?

And: Set_Window command sets the focus to the specified window. We use this command to set the focus to the required window before executing tests on a particular window.

Syntax: set_window(<logical name>, time);

The logical name is the logical name of the window and time is the time the execution has to wait till it gets the given window into focus.

Example:

set_window (“Print”, 12);

button_press (“OK”);

The set_window statement indicates that the Print window is the active window.

The OK button is learned within the context of this window. If you program a test manually, you need to enter the set_window statement then the active window changes. When editing a script, take care not to delete necessary set_window statements.

Q3) How many types of Run Modes are available in WinRunner?

Ans:

WinRunner provide three types of Run Modes. 

Verify Mode

Debug Mode

Update Mode

Q4) How WinRunner identifies GUI objects in an application?

Answer: WinRunner stores information it learns about a window or object in a GUI Map. When WinRunner runs a test, it uses the GUI map to locate objects. It reads an object’s description in the GUI map and then looks for an object with the same properties in the application being tested.

Q5) Please describe WinRunner testing stages.

There are main 6 stages involved in WinRunner testing process.

WinRunner testing stages

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

Recording

Programming

Combining both

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.

Q6) What In Contained In The Gui Map?

WinRunner stores information it learns about a window or object in a GUI Map. When WinRunner runs a test, it uses the GUI map to locate objects. It reads an object’s description in the GUI map and then looks for an object with the same properties in the application being tested. Each of these objects in the GUI Map file will be having a logical name and a physical description. There are 2 types of GUI Map files.

i. Global GUI Map file: a single GUI Map file for the entire application
ii. GUI Map File per Test: WinRunner automatically creates a GUI Map file for each test created

Q7) How Does Winrunner Evaluates Test Results?

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.

Q8) What’s the Verify Mode?

In Verify Mode, WinRunner compare the current result of application to it’s expected result.

Q9) What’s the Debug Mode?

In Debug Mode, WinRunner track the defects in a test script

Q10) What is the Use of Test Director Testing Tool?

TestDirector is Mercury Interactive’s software Test Management Tool. It helps Quality Assurance personnel plan and organizes the testing process. With TestDirector you can create a database of manual and automated tests, build test cycles, run tests, and report and track defects.

You can also create reports and graphs to help review the progress of planning tests, running tests, and tracking defects before a software release.

The best WinRunner Interview Questions and Answers

Q11) What are the Different Modes of Recording in WinRunner?

Two types of Recording in WinRunner:

Context-Sensitive Recording records the operations you perform on your application by identifying the Graphical User Interface (GUI) objects. Windrunner identifies all the objects in your window you click like menus, windows, lists, buttons and the type of operation you perform such as enable, move, select etc.

Analog Recording records keyboard input, mouse clicks, and the precise x- and y-coordinates traveled by the mouse pointer across the screen i.e Winrunner records exact co-ordinates traveled by mouse.

Q12) What is the Purpose of Loading WinRunner Add-Ins?

Add-Ins are used in WinRunner to load functions specific to the particular add-in to the memory. While creating a script only those functions in the add-in selected will be listed in the function generator.

And while executing the script only those functions in the loaded add-in will be executed else WinRunner will give an error message saying it does not recognize the function.

Q13) How do you analyze results and report the defects?

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.

Q15) What is logical name in WinRunner?

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.

Q16) Explain data parameterization in WinRunner.

It is the process of making use of different values in place of recorded values which is replaced by variable which contains different values that can be used during the execution of the scripts. It also reduces the size of the scripts. Parameterization is used when the values and the label of the window changes after every execution like we want to test the application in which order no is involved which is always incremented by 1. Then, in that case we use data parameterization.

Q17) How do I use the WinRunner testing tool?

Therefore recording tests, insert checkpoints where you want to check the behavior of the application under test(AUT). Running Automated test scripts on the build: While running test cases, WinRunner emulates a user by entering mouse and keyboard input into your application.

Q18) How You Integrated Your Automated Scripts From Testdirector?

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.

Q19) How Do You Unload The Gui Map?

We can use GUI_close to unload a specific GUI Map file or else we call use GUI_close_all command to unload all the GUI Map files loaded in the memory.

Syntax: GUI_close(); or GUI_close_all;

Q20) What’s the Context Sensitive recording?

WinRunner captures and records the GUI objects, windows, keyboard inputs, and mouse click activities through Context Sensitive Recording.

Advanced WinRunner Interview Questions and Answers

Q21) What is QTP testing tool?

QTP stands for Quick Test Professional, is a Functional Automation Testing Tool from HP. We can automate functionality of the application by recording the actions on application, developing scripts. Good for automating regression test cases. Scripting language used VB Script which is easily understood by the testers.

Q22) What is the purpose of GUI spy?

Using the GUI Spy, you can view the properties of any GUI object on your desktop. You use the Spy pointer to point to an object, and the GUI Spy displays the properties and their values in the GUI Spy dialog box. You can choose to view all the properties of an object, or only the selected set of properties that WinRunner learns.

Q23) Have you performed debugging of the scripts? 

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.

Q24) How do you run your test scripts?

We run tests in Verify mode to test your application. Each time WinRunner encounters a checkpoint in the test script, it compares the current data of the application being tested to the expected data captured earlier. If any mismatches are found, WinRunner captures them as actual results.

Q25) How do you handle TSL Functions?

Suppose you are running a batch test on an unstable version of your application. If your application crashes, you want WinRunner to recover test execution. A TSL exception can instruct WinRunner to recover test execution by exiting the current test, restarting the application, and continuing with the next test in the batch.

The handler function is responsible for recovering test execution. When WinRunner detects a specific error code, it calls the handler function. You implement this function to respond to the unexpected error in the way that meets your specific testing needs.

Q26) How do you handle pop-up exceptions?

A pop-up exception Handler handles the pop-up messages that come up during the execution of the script in the AUT. TO handle this type of exception we make WinRunner learn the window and also specify a handler to the exception. It could be

Default actions: WinRunner clicks the OK or Cancel button in the pop-up window, or presses Enter on the keyboard. To select a default handler, click the appropriate button in the dialog box.

User-defined handler: If you prefer, specify the name of your own handler. Click User Defined Function Name and type in a name in the User Defined Function Name box.

Q27) What are the three modes of running the scripts?

WinRunner provides three modes in which to run tests: Verify, Debug, and Update. You use each mode during a different phase of the testing process.

Verify

Use the Verify mode to check your application.

Debug

Use the Debug mode to help you identify bugs in a test script.

Update

Use the Update mode to update the expected results of a test or to create a new expected results folder.

Q28) WITHOUT the GUI map, use the phy desc directly?

It’s easy, just take the description straight out of the GUI map squigglies and all, put it into a variable (or pass it as a string) and use that in place of the object name.

button_press ( “btn_OK” );

becomes

button_press (“{class: push_button, label: OK}”);

Q29) How to force WinRunner to learn the sub-items on a menu?

If WinRunner is not learning sub-items then the easy way id to add manually those sub items in to GUI map.. of course you need to study the menu description and always add the PARENT menu name for that particular sub-menu.

Q30) What JDK versions does WinRunner 7.x support? 

WinRunner 7.x supports JDK 1.1.7 through 1.3.1. 

Q31) Can WinRunner 7.x work with TestDirector 7.x?

What JDK versions does WinRunner 7.x support? 

WinRunner 7.x supports JDK 1.1.7 through 1.3.1. 

Q32) Can WinRunner 7.x work with TestDirector 7.x?

Yes, WinRunner 7.x and TestDirector 7.x are fully integrated. 

Related Interview Questions

  1. Apigee Interview Questions
  2. Cloud Foundry Interview Questions And Answers
  3. Actimize Interview Questions
  4. Kibana Interview Questions
  5. Nagios Interview Questions
  6. Jenkins Interview Questions
  7. Chef Interview Questions
  8. Puppet Interview Questions
  9. DB2 Interview Questions
  10. AnthillPro Interview Questions
  11. Angular 2 Interview Questions
  12. Hibernate Interview Questions
  13. ASP.NET Interview Questions
  14. PHP Interview Questions
  15. Kubernetes Interview Questions
  16. Docker Interview Questions
  17. CEH Interview Questions
  18. CyberArk Interview Questions
  19. Appian Interview Questions
  20. Drools Interview Questions
  21. Talend Interview Questions
  22. Selenium Interview Questions
  23. Ab Initio Interview Questions
  24. AB Testing Interview Questions
  25. Mobile Application Testing Interview Questions
  26. Pega Interview Questions
  27. UI Developer Interview Questions
  28. Tableau Interview Questions
  29. SAP ABAP Interview Questions
  30. Reactjs Interview Questions
  31. UiPath Interview Questions

LEAVE A REPLY

Please enter your comment!
Please enter your name here