What do you verify with the bitmap checkpoint for screen area and what
command it generates, explain syntax?
You can define any rectangular area
of the screen and capture it as a bitmap for comparison. The area can be any
size: it can be part of a single window, or it can intersect several windows.
The rectangle is identified by the coordinates of its upper left and lower right
corners, relative to the upper left corner of the window in which the area is
located. If the area intersects several windows or is part of a window with no
title (for example, a popup window), its coordinates are relative to the entire
screen (the root window).
To capture an area of the screen as
Choose Create > Bitmap Checkpoint >
For Screen Area or click the Bitmap Checkpoint for Screen Area button.
Alternatively, if you are recording in Analog mode, press the CHECK BITMAP OF
SCREEN AREA softkey. The WinRunner window is minimized, the mouse pointer
becomes a crosshairs pointer, and a help window opens.
Mark the area to be captured:
press the left mouse button and drag the mouse pointer until a rectangle
encloses the area; then release the mouse button.
Press the right mouse button to
complete the operation. WinRunner captures the area and generates a
win_check_bitmap statement in your script.
The win_check_bitmap statement
for an area of the screen has the following syntax:
win_check_bitmap ( window, bitmap, time, x, y,
width, height );
What do you verify with the database checkpoint default and what command
it generates, explain syntax?
By adding runtime database record
checkpoints you can compare the information in your application during a test
run with the corresponding record in your database. By adding standard database
checkpoints to your test scripts, you can check the contents of databases in
different versions of your application.
When you create database
checkpoints, you define a query on your database, and your database checkpoint
checks the values contained in the result set. The result set is set of values
retrieved from the results of the query.
You can create runtime database
record checkpoints in order to compare the values displayed in your application
during the test run with the corresponding values in the database. If the
comparison does not meet the success criteria you
specify for the checkpoint, the
checkpoint fails. You can define a successful runtime database record checkpoint
as one where one or more matching records were found, exactly one matching
record was found, or where no matching records are found.
You can create standard database
checkpoints to compare the current values of the properties of the result set
during the test run to the expected values captured during recording or
otherwise set before the test run. If the expected results and the current
results do not match, the database checkpoint fails. Standard database
checkpoints are useful when the expected results can be established before the
You can add a runtime database
record checkpoint to your test in order to compare information that appears in
your application during a test run with the current value(s) in the
corresponding record(s) in your database. You add runtime database record
checkpoints by running the Runtime Record Checkpoint wizard. When you are
finished, the wizard inserts the appropriate db_record_check statement
into your script.
A file created by WinRunner and saved in the test's checklist folder. The file
contains information about the data to be captured during the test run and its
corresponding field in the database. The file is created based on the
information entered in the Runtime Record Verification wizard.
Contains one of the following values:
DVR_ONE_OR_MORE_MATCH - The checkpoint passes if one or more matching
database records are found.
DVR_ONE_MATCH - The checkpoint passes if exactly one matching database
record is found.
DVR_NO_MATCH - The checkpoint passes if no matching database records are
An out parameter returning the number of records
in the database.