Winrunner manual pdf

WinRunner is automation tool, specifically a regression test tool. Used to automate the execution of test cases through scripts in TSL WinRunner is an integrated, functional testing tool for the entire enterprise; by capturing, verifying and replaying user interactions automatically. WinRunner dramatically speeds up the testing process.

As WinRunner runs tests, it simulates a human user by moving the mouse cursor over the application, clicking Graphical User Interface GUI objects, and entering keyboard inputbut WinRunner does this faster than any human user. Running test manually again and again is frustrating! Running test manually is prone to making mistakes. Write once, run as many times as needed!

I have more time now Time saving! AUT is made of UI controls as lists, button controls, edit controls etc. WR needs a mechanism to identify the screen objects of AUT. WR records objects using physical description; uses only those that uniquely identifies the object an not others as height etc Why?

Spy is a utility to confirm that WR is recording the objects right. A tool used to look for the object description. How do I use SPY? Launch it from the WR. Multiple tests can reference a common GUI map file Recommended for advanced users.

There are other reasons too. You do not need to worry about creating, saving, and loading GUI map files Recommended for beginners. Alternatively, you can add descriptions of individual objects to the GUI map by clicking objects while recording a test.

Create Tests Next, you create test scripts by recording, programming, or a combination of both. While recording tests, insert checkpoints where you want to check the response of the application being tested.

You can insert checkpoints that check GUI objects, bitmaps, and databases. During this process, WinRunner captures data and saves it as expected resultsthe expected response of the application being tested. Debug Tests You run tests in Debug mode to make sure they run smoothly. Test results are saved in the debug folder, which you can discard once you finished debugging the test. Run Tests You 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. View Results You determine the success or failure of the tests. 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.

In cases of bitmap mismatches, you can also view a bitmap that displays only the difference between the expected and actual results. Report Defects 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. After several seconds, the WinRunner window opens. This engine establishes and maintains the connection between WinRunner and the application being tested.

You create and run WinRunner tests in the test window. It contains the following key elements:. The recording process enables anyone to create and automate tests, so that even users with limited technical background can produce tests. WinRunner includes two modes for Recording tests: Context.

Every time you perform an operation on the application being tested, a TSL statement describing the object selected and the action performed is generated in the test script. Analog mode records mouse clicks, keyboard input, and the exact x- and ycoordinates traveled by the mouse. When the test is run, WinRunner retraces the mouse tracks.

Use Analog mode when exact mouse coordinates are important to your test, such as when testing a drawing application. Mercury WinRunner - Kamran Khan If you are testing an application that contains both GUI objects and bitmap areas, you can switch between modes as you record. It systematically opens the windows in your application and learns the description of every GUI object. The wizard stores this information in a GUI map file.

It automatically generates tests based on the information it learned as it navigated through the application.

The User Interface test determines whether the application complies with the Microsoft user interface standards. It checks that:. Click Next in the wizards Welcome screen to advance to the next screen Point to the application you want to test. Click the button and then click anywhere in the application.

The applications window name appears in the wizards Window Name box. Click Next. The wizard can automatically generate tests. The User Interface test will check that the application complies with Microsoft user interface standards. Accept the default Navigation Controls if you do not need to define additional controls. Click Next The learning flow determines how WinRunner walks through your application. Two modes are available: Express and Comprehensive.

Comprehensive mode lets you customize how the wizard learns GUI object descriptions. First-time WinRunner users should use Express mode. Click the Learn button. The wizard begins walking through the application, pulling down menus, opening windows, and learning object descriptions.

This process takes a few minutes. The wizard also creates a startup script. This script runs automatically each time you start WinRunner.

It contains a command that loads the GUI map file so that WinRunner will be ready to test your application. Use Verify mode when running a test to check the behavior of your application, and when you want to save the test results. Use Debug mode when you want to check that the test script runs smoothly without errors in syntax.

Use Update mode when you want to create new expected results for a GUI checkpoint or bitmap checkpoint. Check that WinRunner and the application are still open on your desktop There are two options for running the User Interface Test. Define the name of the directory in which WinRunner will store the results of the test. Accept the default name e. Click OK in the Run Test dialog box.

WinRunner immediately begins running the UI test. Watch how WinRunner opens each window in the application. Operations recorded in terms of GUI objects. WR identifies each object you click button etc and each operation you perform button click etc. Normally we use Context Sensitive Mode but if the application requires some special actions as signature of user on a sign-pad then user Analog mode.

A login script that is recorded for a AUT may need to be run again with different role login id and password. Manually write the TSL code err.. Debug Update To updated expected values Enhance script by adding functions Adding checkpoints and putting custom messages on report.

To verify the test actual results we use check points They compare the actual results with expected results Set the test case status to pass or fail based on checkpoint A script is useless without checkpoint. Various checkpoints - By adding GUI checkpoints to your test scripts, you can compare the behavior of GUI objects in different versions of your application.

You can check a single property of a GUI object. For example, you can check whether a button is enabled or disabled or whether an item in a list is selected. Click an object. The Check Property dialog box opens and shows the default function for the selected object.

WinRunner automatically assigns argument values to the function. You can modify the arguments for the property check. To modify assigned argument values, choose a value from the Attribute list. The expected value is updated in the Expected text box. Click Paste to paste the statement into your test script. The function is pasted into the script at the insertion point. The Check Property dialog box closes. You can create a GUI checkpoint that performs a default check on the property recommended by WinRunner.

For example, if you create a GUI checkpoint that checks a push button, the default check verifies that the push button is enabled. The WinRunner window is minimized, the mouse pointer becomes a pointing hand, and a help window opens on the screen.

WinRunner captures the current value of the property of the GUI object being checked and stores it in the tests expected results folder. You can specify which properties to check for an object. For example, if you create a checkpoint that checks a push button, you can choose to verify that it is in focus, instead of enabled. Double-click the object or window. The Check GUI dialog box opens.

By adding Bitmap checkpoints to your test scripts, you can compare the Bitmap in different versions of your application. Property value synchronization points When you want WinRunner to wait for an object or a window to have a specified property, you create a property value synchronization point. Bitmap synchronization points. When you want WinRunner to wait for a visual cue to be displayed, you create a bitmap synchronization point.

In a bitmap synchronization point, WinRunner waits for the bitmap of an object, a window, or an area of the screen to appear. By Capturing the text from screen area. Step by step Breakpoints Watch list Add objects and write custom code Modify existing objects definition.

TD connection What is TD? WR can connect to TD. TD can launch WR and hence execute scheduled tests. Batch mode runs scripts in batch mode. Before continuing with this tutorial, you ought to have an essential comprehension of the product improvement life cycle SDLC. Likewise, you ought to have a fundamental comprehension of programming utilizing any programming dialect. Winrunner Tutorial. Job Recommendation Latest. Jobs in Meghalaya Jobs in Shillong.

View All Locations. How to design your resume? Have you ever lie on your resume? Read This Tips for writing resume in slowdown What do employers look for in a resume? Interview Tips 5 ways to be authentic in an interview Tips to help you face your job interview Top 10 commonly asked BPO Interview questions 5 things you should never talk in any job interview Best job interview tips for job seekers 7 Tips to recruit the right candidates in 5 Important interview questions techies fumble most What are avoidable questions in an Interview?

Top 10 facts why you need a cover letter? Username Password. New to Wisdomjobs? Sign up. LoadRunner Tutorial. HTML Tutorial. QTP Tutorial. LoadRunner Interview Questions. WinRunner Interview Questions.

QTP Interview Questions. Manual Testing Interview Questions. OpenStack Interview Questions. Automation Testing Interview Questions.