Winrunner Testing Tool
This is part of the post, “WinRunner Interview questions and answers series ” HP WinRunner automation tool was owned by Mercury Interactive. When HP acquired Mercury Interactive, they stopped Winrunner support and suggested to use the HP Functional Testing software. These are some important WinRunner interview questions frequently asked in automation testing interview. If you are unclear of any answer ask me for clarification.
I will continue this WinRunner tutorial posting series on weekends as a testing interview preparation series for you. How do you analyze test results in Winrunner tool and report the defects? When you finish any test in WinRunner, WinRunner displays the results in a report format. The report logs the general information about the test run.ie, date, operator mode and total run time.
• WinRunner is a test automation tool, designed to help customers save testing time and effort by automating the manual testing process. • Automated testing with WinRunner addresses the problems by manual testing, speeding up the testing process. Testing Automation: Software testing can be very costly. Automation is a good way to cut down time and cost. Automation is a good way to cut down time and cost. Software testing tools and techniques usually suffer from a lack of generic applicability and scalability. Introduction to HP WinRunner Posted in: one response HP / Mercury Interactive’s WinRunner is an automated functional GUI testing tool that allows a user to record and play back UI interactions as test scripts.
Also, the report details all the major events that occurred during the run, such as checkpoints, error messages, system messages, or user messages. A mismatch can be found in the report panel by seeing the actual result and the expected result. If a test run fails due to a defect in the application being tested, you can report information about the defect directly from the Test Results window. This information is sent via e-mail to the quality assurance manager, who tracks the defect until it is fixed. 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. How to integrate automated scripts from TestDirector to Windrunner Scripts?
When you work in WinRunner and create any test script you have the option to save it directly to the Test Director test repository. 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 like TSL(Test Script language) of WinRunner that can be later modified into one which could be used to test the application. What are the different modes of recording in WinRunner? Two types of recording in WinRunner: 1.
Context Sensitive recording records the operations you perform on your application by identifying 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. 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. What are the reasons that WinRunner fails to identify GUI object? WinRunner fails to identify an object in a GUI due to various reasons: 1.
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.
Winrunner Testing Tool Ppt
What do you mean by the logical name of the object? When you click an object, WinRunner assigns the object a logical name, which is usually the object’s text label. The logical name makes it easy for you to read the test script. For Example,when you selected the Order No. Checkbox, WinRunner recorded the following statement in WinRunner TSL: button_set (“Order No.”, ON); “Order No.” is the object’s logical name.