WR Testing Tutorial

WR History
WR Integrations

WR Testing

WR Testing Process
WR Recording
WR CheckPoints
WR FunctionGen
WRGUI Spy
WR GUI Map
WR GUI Configuration
WR V User Object
WR Data Driven Test
WR Parameterization
WR TSL
Learn More...

WR Examples(Script)

WR Script1
WR Script2
WR Script3
WR Script4
WR Script5
WR Script6
WR Script7
WR Script8
WR Script9
WR Script10
WR Examples More...

WR Interview Q&As
WR Q&As1
WR Q&As2
WR Q&As3
WR Q&As4
WR Q&As5
WR Q&As6
WR Q&As7
WR Q&As8
WR Q&As9
WR Q&As10
WR Q&As11
WR Q&As12
WR Q&As13
WR Q&As14
WR Q&As15
WR Q&As16
WR Q&As17
WR Q&As18
WR Q&As19
WR Q&As20
WR Q&As More...

WR FAQ(mp3)
Listen WR FAQ1
Listen WR FAQ2
Listen WR FAQ3
Listen WR FAQ4
Listen WR FAQ5
Listen WR FAQ6
Listen WR FAQ7
Listen WR FAQ8
Listen WR FAQ9
Listen WR FAQ10
Listern More on WR
pixels

THE LARGEST SOFTWARE TESTING SITE ON THE NET

KabInfo.Net  - Full Testing Tutorials - All Free

 

At KabInfo.Net you will find all the Manual and Automation Testing tutorials,
from basic Testing Definition and Testing Types,Testing Methodologies to advanced  Automation Tools like, WinRunner, LoadRunner and a Test Management Tool like TestDirector.

KabInfo.Net - The Largest Enterprise Application Testers site on the Net

Best Tester:- who gets the most bugs fixed :: Smart Tester:- Balances between listening and implementing

:::

KabInfo.Net                                     

 

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 );

 

KabInfo.Net                                     

 

:::

Where to Start

What does a Software Test Engineer have to know? What will the future bring?

KabInfo.Net will try to answer this, and help you become a professional Software Test Engineer, well prepared for the future.

Before you study the tutorials, Read this introduction.

:::

Quick and Easy Learning

Because time is valuable, we deliver quick and easy learning. At KabInfo.Net, you can study everything you need to learn, in an accessible and handy format.

                        "No One Is Great, And Every One Is GREAT"

K.A.Babu (2004)

:::

Testing Joke

Tester : "I Delivered a 100% Bug Free Product!"

:::

KabInfo.Net - Testing School is for self training only. We do not warrant the correctness of the content. The risk of using it remains entirely with the user. While using this site, you agree to have read and accepted our terms of use and privacy policy.

Copyright 2004 . All Rights Reserved.

Logo Courtesy - Venkat Battu

KAB SEARCH

                     About KabInfo.Net
KabInfo downloads

REFERENCES
Test Case Doc
Test Plan Doc
B.R.S/B.R.D
Fun.Spec/Fun.Doc
System Req. Spec. Design Doc
Bug Report
Check List
Test Discussions Doc
.....Other Docs

Listen Testing


After A Bug Is Found
Integreation Testing
Quality
Software Life Cycle
Test Engineer
Types Of Testing
Unit Testing
Testing Concepts
WinRunner
QTP
More MP3s soon...
Q & A Section

Teting
Manual Testing
Automation
WinRunner
LoadRunner
TestDirector
Q.T.P
SQL
CERTIFICATION(S)

CSQA Certification
CSTE Certification
CSPM Certification
VALIDATION
Validate Date
Validate ComboBox
Validate Traingle
Validate Login   Validate E-Mail
Freshers
Seeking S/W Testing Job?

 
 

pixels  

Best Tester???