WinRunner

There are 2 modes of recording in WinRunner

1. Context Sensitive recording records the operations you perform on your application by identifying Graphical User Interface (GUI) objects.

2. Analog recording records keyboard input, mouse clicks, and the precise x- and y-coordinates traveled by the mouse pointer across the screen.

GUI Map editor displays the content of a GUI Map. We can invoke GUI Map Editor from the Tools Menu in WinRunner. The GUI Map Editor displays the various GUI Map files created and the windows and objects learned in to them with their logical name and physical description.

The checklist file contains information about the objects and the properties of the object we are verifying.

The gui*.chk file contains the expected results which is stored in the exp folder

* When you create a custom check on a database, you create a standard database checkpoint in which you can specify which properties to check on a result set.

* You can create a custom check on a database in order to:

o check the contents of part or the entire result set

o edit the expected results of the contents of the result set

o count the rows in the result set

o count the columns in the result set

* You can create a custom check on a database using ODBC, Microsoft Query or Data Junction.

The difference between bitmaps option in the Run Tab of the general options defines the minimum number of pixels that constitute a bitmap mismatch

You can create a bitmap synchronization point that waits for the bitmap of an object or a window to appear in the application being tested.

During a test run, WinRunner suspends test execution until the specified bitmap is redrawn, and then compares the current bitmap with the expected one captured earlier. If the bitmaps match, then WinRunner continues the test.

Syntax:

obj_wait_bitmap ( object, image, time );

win_wait_bitmap ( window, image, time );

The extension for a GUI Map file is “.gui”.