|
1)
What do you verify with the GUI checkpoint for object/window and what
command it generates, explain syntax?
a)
You can create a GUI checkpoint to
check a single object in the application being tested. You can either check the
object with its default properties or you can specify which properties to check.
b)
Creating a GUI Checkpoint
using the Default Checks
i.
You can create a GUI checkpoint
that performs a default check on the property recommended by WinRunner. For
example, if you create a GUI checkpoint that checks a push button, the default
check verifies that the push button is enabled.
ii.
To create a GUI checkpoint
using default checks:
1.
Choose Create > GUI Checkpoint > For Object/Window, or click the GUI
Checkpoint for Object/Window button on the User toolbar. If you are recording in
Analog mode, press the CHECK GUI FOR OBJECT/WINDOW softkey in order to avoid
extraneous mouse movements. Note that you can press the CHECK GUI FOR
OBJECT/WINDOW softkey in Context Sensitive mode as well. The WinRunner window is
minimized, the mouse pointer becomes a pointing hand, and a help window opens on
the screen.
2.
Click an object.
3.
WinRunner captures the current value of the property of the GUI object
being checked and stores it in the test’s expected results folder. The WinRunner
window is restored and a GUI checkpoint is inserted in the test script as an
obj_check_gui statement
Syntax:
win_check_gui ( window, checklist, expected_results_file, time );
c)
Creating a GUI Checkpoint by
Specifying which Properties to Check
d)
You can specify which properties to
check for an object. For example, if you create a checkpoint that checks a push
button, you can choose to verify that it is in focus, instead of enabled.
e)
To create a GUI checkpoint by
specifying which properties to check:
i.
Choose Create > GUI Checkpoint
> For Object/Window, or click the GUI Checkpoint for Object/Window button on the
User toolbar. If you are recording in Analog mode, press the CHECK GUI FOR
OBJECT/WINDOW softkey in order to avoid extraneous mouse movements. Note that
you can press the CHECK GUI FOR OBJECT/WINDOW softkey in Context Sensitive mode
as well. The WinRunner window is minimized, the mouse pointer becomes a pointing
hand, and a help window opens on the screen.
ii.
Double-click the object or
window. The Check GUI dialog box opens.
iii.
Click an object name in the
Objects pane. The Properties pane lists all the properties for the selected
object.
iv.
Select the properties you want
to check.
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 (three dots) 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.
4.
Click OK to close the Check GUI dialog box. WinRunner captures the GUI
information and stores it in the test’s expected results folder. The WinRunner
window is restored and a GUI checkpoint is inserted in the test script as an
obj_check_gui or a win_check_gui statement.
Syntax:
win_check_gui ( window, checklist, expected_results_file, time );
obj_check_gui ( object, checklist, expected
results file, time );
|
