[Spoorthi]

62) What do you verify with the GUI checkpoint for multiple objects and
what command it generates, explain syntax?[/b]


a. To
create a GUI checkpoint for two or more objects:[/b]


i. Choose Create > GUI Checkpoint > For
Multiple Objects or click the GUI Checkpoint for Multiple Objects button on the
User toolbar. If you are recording in Analog mode, press the CHECK GUI FOR
MULTIPLE OBJECTS softkey in order to avoid extraneous mouse movements. The
Create GUI Checkpoint dialog box opens.


ii. Click the Add button. The mouse pointer becomes
a pointing hand and a help window opens.


iii. To add an object, click it once. If you click a
window title bar or menu bar, a help window prompts you to check all the
objects in the window.


iv. The pointing hand remains active. You can
continue to choose objects by repeating step 3 above for each object you want
to check.


v. Click the right mouse button to stop the selection
process and to restore the mouse pointer to its original shape. The Create GUI
Checkpoint dialog box reopens.


vi. The Objects pane contains the name of the
window and objects included in the GUI checkpoint. To specify which objects to
check, click an object name in the Objects pane. The Properties pane lists all
the properties of the object. The default properties are selected.


1. To edit the expected value of a property, first
select it. Next, either click the Edit Expected Value button, or double-click
the value in the Expected Value column to edit it.


2. To add a check in which you specify arguments,
first select the property for which you want to specify arguments. Next, either
click the Specify Arguments button, or double-click in the Arguments column.
Note that if an ellipsis appears in the Arguments column, then you must specify
arguments for a check on this property. (You do not need to specify arguments
if a default argument is specified.) When checking standard objects, you only
specify arguments for certain properties of edit and static text objects. You
also specify arguments for checks on certain properties of nonstandard objects.



3. To change the viewing options for the
properties of an object, use the Show Properties buttons.


vii. To save the checklist and close the Create GUI
Checkpoint dialog box, click OK. WinRunner captures the current property values
of the selected GUI objects and stores it in the expected results folder. A
win_check_gui statement is inserted in the test script.





Syntax[/b]:
win_check_gui ( window, checklist,
expected_results_file, time );[/i]


[/b]obj_check_gui ( object, checklist, expected results file, time ); [/i]

[Spoorthi]

63) What information is contained in the checklist file and in which
file expected results are stored?[/b]


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


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

[Spoorthi]

64) What do you verify with the bitmap check point for object/window and
what command it generates, explain syntax?[/b]


a. You can check an object, a window, or an
area of a screen in your application as a bitmap. While creating a test, you
indicate what you want to check. WinRunner captures the specified bitmap,
stores it in the expected results folder (exp) of the test, and inserts a
checkpoint in the test script. When you run the test, WinRunner compares the
bitmap currently displayed in the application being tested with the expected
bitmap stored earlier. In the event of a mismatch, WinRunner captures the
current actual bitmap and generates a difference bitmap. By comparing the three
bitmaps (expected, actual, and difference), you can identify the nature of the
discrepancy.


b. When working in Context Sensitive mode,
you can capture a bitmap of a window, object, or of a specified area of a
screen. WinRunner inserts a checkpoint in the test script in the form of either
a win_check_bitmap or obj_check_bitmap statement.


c. Note that when you record a test in Analog
mode, you should press the CHECK BITMAP OF WINDOW softkey or the CHECK BITMAP
OF SCREEN AREA softkey to create a bitmap checkpoint. This prevents WinRunner
from recording extraneous mouse movements. If you are programming a test, you
can also use the Analog function check_window to check a bitmap.





d. To
capture a window or object as a bitmap:[/b]


[/b]


i. Choose Create > Bitmap Checkpoint > For
Object/Window or click the Bitmap Checkpoint for Object/Window button on the
User toolbar. Alternatively, if you are recording in Analog mode, press the
CHECK BITMAP OF OBJECT/WINDOW softkey. The WinRunner window is minimized, the
mouse pointer becomes a pointing hand, and a help window opens.


ii. Point to the object or window and click it.
WinRunner captures the bitmap and generates a win_check_bitmap or
obj_check_bitmap statement in the script. The TSL statement generated for a
window bitmap has the following syntax:


win_check_bitmap ( object,
bitmap, time );


iii. For an object bitmap, the syntax is:


obj_check_bitmap ( object, bitmap, time );


iv. For example, when you click the title bar of
the main window of the Flight Reservation application, the resulting statement
might be:


win_check_bitmap ("Flight
Reservation", "Img2", 1);


v. However, if you click the Date of Flight box
in the same window, the statement might be:


obj_check_bitmap
("Date of Flight:", "Img1", 1);





Syntax[/b]: obj_check_bitmap ( object,
bitmap, time [, x, y, width, height] );[/i]


[/b]


[/b]

[Spoorthi]

65) What do you verify with the bitmap
checkpoint for screen area and what command it generates, explain syntax?[/b]


a. 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).





b. To
capture an area of the screen as a bitmap:[/b]


[/b]


i. 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.


ii. 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.


iii. Press the right mouse button to complete the
operation. WinRunner captures the area and generates a win_check_bitmap
statement in your script.


iv. The win_check_bitmap statement for an area of
the screen has the following syntax:


[/i]


win_check_bitmap ( window,
bitmap, time, x, y, width, height );[/i]


[/i]

[Spoorthi]

66) What do you verify with the database checkpoint default and what
command it generates, explain syntax?[/b]


a. 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.


b. 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.


c. 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


d. 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.


e. 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
test run.





Syntax[/b]:
db_check(<checklist_file>,
<expected_restult>);[/i]





f. 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[/b]
statement into your script.





Syntax :[/b] db_record_check(ChecklistFileName,SuccessConditions,RecordNu mber );[/i]


ChecklistFileName[/b] 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.


SuccessConditions [/b]Contains one of the following values:


1. DVR_ONE_OR_MORE_MATCH - The checkpoint passes
if one or more matching database records are found.


2. DVR_ONE_MATCH - The checkpoint passes if
exactly one matching database record is found.


3. DVR_NO_MATCH - The checkpoint passes if no
matching database records are found.


RecordNumber [/b]An out parameter returning the number of records in the database.

[Spoorthi]

67) How do you handle dynamically changing area of the window in the
bitmap checkpoints?[/b]


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.

[Spoorthi]

68) What do you verify with the database check point custom and what
command it generates, explain syntax?[/b]


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.

[Spoorthi]

69) What do you verify with the sync point for object/window property
and what command it generates, explain syntax?[/b]


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:[/b]


obj_exists ( object [, time ] );[/i]


win_exists ( window [, time ] );[/i]


[/i]

[Spoorthi]

70) What do you verify with the sync point for object/window bitmap and
what command it generates, explain syntax?[/b]


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:[/b]


obj_wait_bitmap ( object, image, time );[/i]


win_wait_bitmap ( window, image, time [/i]);

[Spoorthi]

71) What do you verify with the sync point for screen area and what
command it generates, explain syntax?[/b]


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: [/b]obj_wait_bitmap(object,
image, time, x, y, width, height);[/i]

[Spoorthi]

72) How do you edit checklist file and when do you need to edit the
checklist file?[/b]


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.

[Spoorthi]

73) How do you edit the expected value of an object?[/b]


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.





74) How do you modify the expected results of a GUI checkpoint?[/b]


a. We can modify the expected results of a GUI
checkpoint be running the script containing the checkpoint in the update mode.

[Spoorthi]

75) How do you handle ActiveX and Visual basic objects?[/b]


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.


[/b]


76) How do you create ODBC query?[/b]


a. We can create ODBC query using the database
checkpoint wizard. It provides with option to create an SQL file that uses an
ODBC DSN to connect to the database. The SQL File will contain the connection
string and the SQL statement.

[Spoorthi]

77) How do you record a data driven test?[/b]


a. We can create a data-driven testing using
data from a flat file, data table or a database.


i. Using
Flat File[/b]: we actually store the data to be used in a required format in
the file. We access the file using the File manipulation commands, reads data
from the file and assign the variables with data.


ii. Data
Table: [/b]It is an excel file. We can store test data in these files and
manipulate them. We use the ‘ddt_*[/b]’ functions to manipulate data in the data
table.


iii.
Database:[/b] we store test data in the
database and access these data using ‘db_*[/b]’
functions.

[Spoorthi]

78) How do you convert a database file to a text file?[/b]


a. You can use Data Junction to create a
conversion file which converts a database to a target text file.





79) How do you parameterize database check points?[/b]


a. When you create a standard database
checkpoint using ODBC (Microsoft Query), you can add parameters to an SQL
statement to parameterize the checkpoint. This is useful if you want to create
a database checkpoint with a query in which the SQL statement defining your
query changes.