|
1)
How do you handle dynamically changing area of the window in the bitmap
checkpoints?
a)
The difference between bitmaps
option in the Run Tab of the general options defines the minimum number of
pixels that constitute a bitmap mismatch
2)
What do you verify with the database check point custom and what command
it generates, explain syntax?
a)
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.
b)
You can create a custom check on a
database in order to:
i.
check the contents of part or
the entire result set
ii.
edit the expected results of
the contents of the result set
iii.
count the rows in the result
set
iv.
count the columns in the result
set
c)
You can create a custom check on a
database using ODBC, Microsoft Query or Data Junction.
3)
What do you verify with the sync point for object/window property and
what command it generates, explain syntax?
a)
Synchronization compensates for
inconsistencies in the performance of your application during a test run. By
inserting a synchronization point in your test script, you can instruct
WinRunner to suspend the test run and wait for a cue before continuing the test.
b)
You can a synchronization point
that instructs WinRunner to wait for a specified object or window to appear. For
example, you can tell WinRunner to wait for a window to open before performing
an operation within that window, or you may want WinRunner to wait for an object
to appear in order to perform an operation on that object.
c)
You use the obj_exists function to
create an object synchronization point, and you use the win_exists function to
create a window synchronization point. These functions have the following
syntax:
Syntax:
obj_exists ( object [, time ] );
win_exists ( window [, time ] );
4)
What do you verify with the sync point for object/window bitmap and what
command it generates, explain syntax?
a)
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.
b)
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
);
5)
What do you verify with the sync point for screen area and what command
it generates, explain syntax?
a)
For screen area verification we
actually capture the screen area into a bitmap and verify the application screen
area with the bitmap file during execution
Syntax:
obj_wait_bitmap(object, image, time, x, y, width,
height);
6)
How do you edit checklist file and when do you need to edit the checklist
file?
a)
WinRunner has an edit checklist
file option under the create menu. Select the “Edit GUI Checklist” to modify GUI
checklist file and “Edit Database Checklist” to edit database checklist file.
This brings up a dialog box that gives you option to select the checklist file
to modify. There is also an option to select the scope of the checklist file,
whether it is Test specific or a shared one. Select the checklist file, click OK
which opens up the window to edit the properties of the objects.
7)
How do you edit the expected value of an object?
a)
We can modify the expected value of
the object by executing the script in the Update mode. We can also manually edit
the gui*.chk file which contains the expected values which come under the exp
folder to change the values.
8)
How do you modify the expected results of a GUI checkpoint?
a)
We can modify the expected results
of a GUI checkpoint be running the script containing the checkpoint in the
update mode.
9)
How do you handle ActiveX and Visual basic objects?
a)
WinRunner provides with add-ins for
ActiveX and Visual basic objects. When loading WinRunner, select those add-ins
and these add-ins provide with a set of functions to work on ActiveX and VB
objects.
|
