If you're looking for WinRunner Interview Questions for Experienced or Freshers, you are in right place. There are a 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 the opportunity to move ahead in your career as Testing Analyst. Mindmajix offers Advanced WinRunner Interview Questions 2022 that helps you in cracking your interview & acquire a dream career as a Quality Assurance Analyst Developer.
|If you want to enrich your career and become a professional in WinRunner, then enroll in "WinRunner training" - This course will help you to achieve excellence in this domain.|
WinRunner developed by HP is a functional and automated GUI testing tool. Using this tool, users can record UI interactions and can replay them as well as test scripts. It is widely used to identify any defects in business processes.
There are main 6 stages involved in the 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 runs can make work easy of finding defects.
4. Running test cases in verify mode to test the application and compares the data of the 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.
WinRunner used TSL-Test Script Language. It is similar to C.
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.
WinRunner displays test results in a report. This report lists out all the events that took place during the test run like error messages, checkpoints, user messages, or system messages. In case of any mismatch at a checkpoint, we can compare the expected and actual results in the Test Results window.
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.
Wrun.ini the the file is the setup configuration file for WinRunner.
Set_window is used to set the focus on any window. This command is used to place focus on the specified window before implementing any test scripts.
set_window (, )
There can be few cases where WinRunner won’t be able to identify GUI objects.
The logical name of any object is nothing but the text label of that object. This makes the code easily understandable and readable.
GUI Map file is a file containing all GUI objects used in the application with their logical names and physical description.
GUI Map is a collection of all GUI Map files.
We can organize GUI Map files in 2 ways
We can load GUI Map by using the command GUI_load ().
Yes, it is possible to unload the 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
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 the GUI Spy dialog box. However, we can filter to see all or selected sets of properties in the dialog box.
GUI Map File’s extension is - “.gui”.
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.
WinRunner provides two ways of recording.
If the object doesn’t have any label/text, then the attached text would be the logical name of that object.
Below are the drawbacks of loading GUI Map files using startup scripts.
When we run any test scripts in WinRunner, WinRunner identifies windows and objects by itself and also loads them into a temporary GUI Map file. We have an option to load this temporary GUI Map File while running any tests.
A checkpoint is a place where we can compare and check the actual and expected results of any tests. There are four types of checkpoints in WinRunner.
Both properties are used to handle constantly changing window labels.
Running Compile Module in WinRunner has few drawbacks as mentioned below.
A boundary test is termed as a test carried to ensure the program’s responses to extreme inputs. It ensures that the program can handle extreme inputs and produce respective outputs at both boundaries.
statusbar_get_text (”Status Bar”, O, statustext);
Here the variable status text contains information in the status bar.
WinRunner provides exception handling to face and detect and unexpected events and to take action accordingly. WinRunner supports the following types of exceptions.
Press “Ctrl+F3” to freeze GUI Spy.
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
Stay updated with our newsletter, packed with Tutorials, Interview Questions, How-to's, Tips & Tricks, Latest Trends & Updates, and more ➤ Straight to your inbox!
|WinRunner Training||Feb 07 to Feb 22|
|WinRunner Training||Feb 11 to Feb 26|
|WinRunner Training||Feb 14 to Mar 01|
|WinRunner Training||Feb 18 to Mar 05|
Ravindra Savaram is a Content Lead at Mindmajix.com. His passion lies in writing articles on the most popular IT platforms including Machine learning, DevOps, Data Science, Artificial Intelligence, RPA, Deep Learning, and so on. You can stay up to date on all these technologies by following him on LinkedIn and Twitter.
Copyright © 2013 - 2023 MindMajix Technologies