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 do you handle unexpected events and errors?

a)        WinRunner uses exception handling to detect an unexpected event when it occurs and act to recover the test run.

Text Box: Define Exception Handling
Text Box: Define Exception
Text Box: Define Handler Function
Text Box: Activate Exception Handling









  WinRunner enables you to handle the following types of exceptions:

 Pop-up exceptions: Instruct WinRunner to detect and handle the appearance of a specific window.

 TSL exceptions: Instruct WinRunner to detect and handle TSL functions that return a specific error code.

 Object exceptions: Instruct WinRunner to detect and handle a change in a property for a specific GUI object.

 Web exceptions: When the WebTest add-in is loaded, you can instruct WinRunner to handle unexpected events and errors that occur in your Web site during a test run.


2)       How do you handle pop-up exceptions?

a)        A pop-up exception Handler handles the pop-up messages that come up during the execution of the script in the AUT. TO handle this type of exception we make WinRunner learn the window and also specify a handler to the exception. It could be

                                                               i.      Default actions: WinRunner clicks the OK or Cancel button in the pop-up window, or presses Enter on the keyboard. To select a default handler, click the appropriate button in the dialog box.

                                                              ii.      User-defined handler: If you prefer, specify the name of your own handler. Click User Defined Function Name and type in a name in the User Defined Function Name box.


3)       How do you handle TSL exceptions?

a)        A TSL exception enables you to detect and respond to a specific error code returned during test execution.

b)        Suppose you are running a batch test on an unstable version of your application. If your application crashes, you want WinRunner to recover test execution. A TSL exception can instruct WinRunner to recover test execution by exiting the current test, restarting the application, and continuing with the next test in the batch.

c)        The handler function is responsible for recovering test execution. When WinRunner detects a specific error code, it calls the handler function. You implement this function to respond to the unexpected error in the way that meets your specific testing needs.

d)        Once you have defined the exception, WinRunner activates handling and adds the exception to the list of default TSL exceptions in the Exceptions dialog box. Default TSL exceptions are defined by the XR_EXCP_TSL configuration parameter in the wrun.ini configuration file.


4)       How do you handle object exceptions?

a)        During testing, unexpected changes can occur to GUI objects in the application you are testing. These changes are often subtle but they can disrupt the test run and distort results.

b)        You could use exception handling to detect a change in property of the GUI object during the test run, and to recover test execution by calling a handler function and continue with the test execution


5)       How do you comment your script?

a)        We comment a script or line of script by inserting a ‘#’ at the beginning of the line.


6)       What is a compile module?

a)        A compiled module is a script containing a library of user-defined functions that you want to call frequently from other tests. When you load a compiled module, its functions are automatically compiled and remain in memory. You can call them directly from within any test.

b)        Compiled modules can improve the organization and performance of your tests. Since you debug compiled modules before using them, your tests will require less error-checking. In addition, calling a function that is already compiled is significantly faster than interpreting a function in a test script.


7)       What is the difference between script and compile module?

a)        Test script contains the executable file in WinRunner while Compiled Module is used to store reusable functions. Complied modules are not executable.

b)        WinRunner performs a pre-compilation automatically when it saves a module assigned a property value of “Compiled Module”.

c)        By default, modules containing TSL code have a property value of "main". Main modules are called for execution from within other modules. Main modules are dynamically compiled into machine code only when WinRunner recognizes a "call" statement. Example of a call for the "app_init" script:

call cso_init();

call( "C:\\MyAppFolder\\" & "app_init" );

d)        Compiled modules are loaded into memory to be referenced from TSL code in any module. Example of a load statement:

 reload (“C:\\MyAppFolder\\" & "flt_lib");


        load ("C:\\MyAppFolder\\" & "flt_lib");





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???