WR Testing Tutorial

WR History
WR Integrations

WR Testing

WR Testing Process
WR Recording
WR CheckPoints
WR FunctionGen
WR GUI Configuration
WR V User Object
WR Data Driven Test
WR Parameterization
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


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




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




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


                     About KabInfo.Net
KabInfo downloads

Test Case Doc
Test Plan Doc
System Req. Spec. Design Doc
Bug Report
Check List
Test Discussions Doc
.....Other Docs

Listen Testing

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

Manual Testing

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



Best Tester???