|
1)
How you created you test scripts 1) by recording or 2) programming?
a)
Programming. I have done complete
programming only, absolutely no recording.
2)
What are the two modes of recording?
a)
There are 2 modes of recording in
WinRunner
i.
Context Sensitive recording
records the operations you perform on your application by identifying Graphical
User Interface (GUI) objects.
ii.
Analog recording records
keyboard input, mouse clicks, and the precise x- and y-coordinates traveled by
the mouse pointer across the screen.
3)
What is a checkpoint and what are different types of checkpoints?
a)
Checkpoints allow you to compare
the current behavior of the application being tested to its behavior in an
earlier version.
You can add four types of checkpoints to your
test scripts:
i.
GUI checkpoints verify
information about GUI objects. For example, you can check that a button is
enabled or see which item is selected in a list.
ii.
Bitmap checkpoints take a
“snapshot” of a window or area of your application and compare this to an image
captured in an earlier version.
iii.
Text checkpoints read text in
GUI objects and in bitmaps and enable you to verify their contents.
iv.
Database checkpoints check the
contents and the number of rows and columns of a result set, which is based on a
query you create on your database.
4)
What are data driven tests?
a)
When you test your application, you
may want to check how it performs the same operations with multiple sets of
data. You can create a data-driven test with a loop that runs ten times: each
time the loop runs, it is driven by a different set of data. In order for
WinRunner to use data to drive the test, you must link the data to the test
script which it drives. This is called parameterizing your test. The data is
stored in a data table. You can perform these operations manually, or you can
use the DataDriver Wizard to parameterize your test and store the data in a data
table.
5)
What are the synchronization points?
a)
Synchronization points enable you
to solve anticipated timing problems between the test and your application. For
example, if you create a test that opens a database application, you can add a
synchronization point that causes the test to wait until the database records
are loaded on the screen.
b)
For Analog testing, you can also
use a synchronization point to ensure that WinRunner repositions a window at a
specific location. When you run a test, the mouse cursor travels along exact
coordinates. Repositioning the window enables the mouse pointer to make contact
with the correct elements in the window.
6)
What is parameterizing?
a)
In order for WinRunner to use data
to drive the test, you must link the data to the test script which it drives.
This is called parameterizing your test. The data is stored in a data table.
7)
How do you maintain the document information of the test scripts?
a)
Before creating a test, you can
document information about the test in the General and Description tabs of the
Test Properties dialog box. You can enter the name of the test author, the type
of functionality tested, a detailed description of the test, and a reference to
the relevant functional specifications document.
8)
What do you verify with the GUI checkpoint for single property and what
command it generates, explain syntax?
a)
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. To create a GUI checkpoint for a
property value, use the Check Property dialog box to add one of the following
functions to the test script:
i.
button_check_info
ii.
scroll_check_info
iii.
edit_check_info
iv.
static_check_info
v.
list_check_info
vi.
win_check_info
vii.
obj_check_info
Syntax:
button_check_info
(button, property, property_value );
edit_check_info ( edit, property,
property_value ); |
