Explore topic-wise InterviewSolutions in .

ANSWER : FUNCTION writeLog(in strMessage) { file_open("C:FILEPATH..."); file_printf(strMessage); PRINTF(strMessage); }

DO NOT use BitMap or GUI Checkpoints for DYNAMIC VERIFICATION. These checkpoints are PURELY for static VERIFICATIONS. There are of course, work-around, but mostly not worth the EFFORT.

DO NOT use BitMap or GUI Checkpoints for dynamic verification. These checkpoints are purely for static verifications. There are of course, work-around, but mostly not worth the effort.

The reload function removes a compiled module from memory, and then loads it again. In effect, reload COMBINES the functions of unload and LOAD.
When you reload a module you can define the module TYPE. The compiled module types are SYSTEM and user.

The reload function removes a compiled module from memory, and then loads it again. In effect, reload combines the functions of unload and load.
When you reload a module you can define the module type. The compiled module types are system and user.

Run tests in VERIFY mode to TEST your application. Each time WinRunner encounters a CHECKPOINT in the test script, it compares the current data of the application being tested to the EXPECTED data captured earlier. If any mismatches are found, WinRunner captures them as actual results.

Run tests in Verify mode to test your application. Each time WinRunner encounters a checkpoint in the test script, it compares the current data of the application being tested to the expected data captured earlier. If any mismatches are found, WinRunner captures them as actual results.

These are the POINTS for choosing automation

• The PROJECT should be LONG term
• The Application should be Stable
• If the Project face more regression TEST, then automation will be helpful, by ramping down the RESOURCES.

These are the Points for choosing automation

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

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

We COMMENT a SCRIPT or LINE of script by INSERTING a ‘#’ at the BEGINNING of the line.

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

Recovery SCENARIO GIVES you an option to TAKE some action for recovering from a fatal error in the test.

Recovery scenario gives you an option to take some action for recovering from a fatal error in the test.

Time_str([EXPRESSION]) FUNCTION will give the day of the WEEK for specific date in WINRUNNER.

Time_str([expression]) function will give the day of the week for specific date in winrunner.

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.

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.

The SEARCH path determines the DIRECTORIES that WinRunner will search for a CALLED TEST.

The search path determines the directories that WinRunner will search for a called test.

Global GUImap file lode in winrunner at the TIME of winrunner invoked. global GUI contains FILES which will be use overall application TESTING. GUI map files use as per your requirement. per SCRIPT or you can ALSO use two different gui files in same split.

Global GUImap file lode in winrunner at the time of winrunner invoked. global GUI contains files which will be use overall application testing. GUI map files use as per your requirement. per script or you can also use two different gui files in same split.

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.

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.

We can CHECK the spellings in winrunner using GUIcheckpoints.
CREATE->GUI CHECKPOINT

We can check the spellings in winrunner using GUIcheckpoints.
create->GUI checkpoint

GUI map EDITOR has a Filter Option. This PROVIDES for filtering with 3 different types of options.

1. Filter by LOGICAL Name: GUI Map editor displays only objects with the specified Logical name
2. Filter by physical DESCRIPTION: GUI Map editor displays only objects that match the physical description Use any substring belonging to the physical description.
3. Filter by Class:GUI Map editor displays objects of the specified class.

GUI map editor has a Filter Option. This provides for filtering with 3 different types of options.

CLASS mapping is nothing but, mapping CUSTOM objects with STANDARD objects.

Class mapping is nothing but, mapping custom objects with standard objects.

Database check Points are used to check the data base if you are updating(adding/deleting/editing) the data from the frontend and in this case you NEED to check all these operations you have done from front end they are updating in the BACK end database or not for this purpose exactly we USE database check points in winrunner there are 3 types of database check points are there:

1.  Default check : It selects the Entire data table as database.
2.  Custom Check : It will Counts total No. of rows and COLUMNS.
3.  runtime : it will check in the run time.

Database check Points are used to check the data base if you are updating(adding/deleting/editing) the data from the frontend and in this case you need to check all these operations you have done from front end they are updating in the back end database or not for this purpose exactly we use database check points in winrunner there are 3 types of database check points are there:

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.

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.

MAIN TEST: This is EXECUTABLE
COMPILE MODULE: This is not executable

Main Test: This is executable
Compile Module: This is not executable

This is where the SYNCHRONIZATION checkpoints come handy.
You could SYNCHRONIZE the application with tool in two ways:

1.  By WAITING for a certain time PERIOD
2.  By waiting for certain things to happens like waiting for appropriate status message to appear etc.

This is where the synchronization checkpoints come handy.
You could synchronize the application with tool in two ways:

auto and static variables.

auto: An auto VARIABLE can be declared only within a function and is local to that function. It exists only for as long as the function is running. A new COPY of the variable is created each TIME the function is called.

static: A static variable is local to the function, test, or compiled MODULE in which it is declared. The variable retains its value until the test is terminated by an Abort command. This variable is initialized each time the definition of the function is executed.

auto and static variables.

auto: An auto variable can be declared only within a function and is local to that function. It exists only for as long as the function is running. A new copy of the variable is created each time the function is called.

static: A static variable is local to the function, test, or compiled module in which it is declared. The variable retains its value until the test is terminated by an Abort command. This variable is initialized each time the definition of the function is executed.

Yes, There is no command in Winrunner for executing the script in notepad but we can call the data from notepad USING FILE functions. One more THING is there is a command for invoking the notepad APPLICATION but there is no command to run the TSL statements in that notepad from winrunner.

Yes, There is no command in Winrunner for executing the script in notepad but we can call the data from notepad using file functions. One more thing is there is a command for invoking the notepad application but there is no command to run the TSL statements in that notepad from winrunner.

Addwatch is used for the purpose of MONITORING the VARIABLE. You can ADD variables, expressions and ARRAYS to the watch list using the add watch dialog box.

Addwatch is used for the purpose of monitoring the variable. You can add variables, expressions and arrays to the watch list using the add watch dialog box.

• in: A parameter that is assigned a VALUE from outside the function.
• out: A parameter that is assigned a value from INSIDE the function.
• INOUT: A parameter that can be assigned a value from outside or inside the function.

WINRUNNER does not SUPPORT data types INSTEAD it has class specifies Auto, Static, Public, EXTERN.

winrunner does not support data types instead it has class specifies Auto, Static, Public, Extern.

1.  Write code using ONE set of DATA or one complete cycle
2.  go for tools and SELECT data driven APPROACH.
3.  Their you will get a WINDOW asking existing database or create new go for existing and select exel sheet
4.  press next it will ask which field to be replaced with which do it and complete

For debugging, execute the SCRIPT in the debug mode. We can also debug script USING the Step, Step Into, Step out functionalities PROVIDED by the WINRUNNER.

For debugging, execute the script in the debug mode. We can also debug script using the Step, Step Into, Step out functionalities provided by the WinRunner.

If there are THOUSANDS of scripts and a CR forces all the scripts to MODIFY accordingly, it's always better to CREATE the GUI files again and record the scenarios, where the CRS affects.

If there are thousands of scripts and a CR forces all the scripts to modify accordingly, it's always better to create the GUI files again and record the scenarios, where the CRs affects.

yes it’s POSSIBLE to HANDLE a results directory in WINRUNNER.

yes it’s possible to handle a results directory in winrunner.

In cases where the obligatory and optional properties do not uniquely identify an object, WinRunner USES a selector to DIFFERENTIATE between them. Two types of selectors are available:

1.  A location selector uses the SPATIAL position of objects.
2.  An INDEX selector uses a UNIQUE number to identify the object in a window.

In cases where the obligatory and optional properties do not uniquely identify an object, WinRunner uses a selector to differentiate between them. Two types of selectors are available:

• Function Generator: It is the library of TSL functions.Some testers USES this option to detect unknown TSL Statements.
• The navigation is as follows: Go to create ----> Insert function ----> From Function Generator ----> Select Category ----> Select function NAME depending on Description ----> Fill Arguments ----> CLICK paste.
• In this manner the unknown TSL Functions can be generated through this navigation.

* preceding INDICATES that the CURING GUI file in L1 needs to be SAVED means some changes have been done to the file and those changes have not been saved YET.

* preceding indicates that the curing GUI file in L1 needs to be saved means some changes have been done to the file and those changes have not been saved yet.

The DIFFERENCE between SIMPLE recovery and COMPOUND recovery is that in compound recovery we can give POST recovery operations.

The difference between Simple recovery and compound recovery is that in compound recovery we can give Post recovery operations.

There are three frameworks in WINRUNNER like

1. DATA Driven FRAMEWORK
2. KEYBOARD framework
3. Hybid framework

There are three frameworks in WinRunner like

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: obj_wait_bitmap(object, IMAGE, time, x, y, width, HEIGHT);

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

For Desktop APPLICATIONS WinRunner SUPPORTS 3 Types of Exceptions i.e.,

1. TSL--> Record TIME Errors
2. Object-->Expected And ACTUAL object is same
3. Pop Up-->Unwanted Windows Errors

For Desktop Applications WinRunner Supports 3 Types of Exceptions i.e.,

Go to File-> Test PROPERTIES->GENERAL, SELECT Compiled Module from the Test type list box and click Apply then OK Button.

Go to File-> Test Properties->General, Select Compiled Module from the Test type list box and click Apply then OK Button.

When you test your APPLICATION, you may WANT to check how it PERFORMS the same operations with MULTIPLE sets of data.

When you test your application, you may want to check how it performs the same operations with multiple sets of data.

The mapping and the configuration you set are valid only for the CURRENT WinRunner session. To MAKE the mapping and the configuration PERMANENT, you MUST add configuration statements to your startup test script.

The mapping and the configuration you set are valid only for the current WinRunner session. To make the mapping and the configuration permanent, you must add configuration statements to your startup test script.

The additional features winrunner 8.0 supports

1.  SUPPORT for Netscape 7.x
2.  Support for POWER builder
3.  Advance function VIEWER window
4.  More PRINTING options
5.  support for windows 2003

The additional features winrunner 8.0 supports

First they will CONDUCT

• Functionality TESTING
• Input Domain Testing
• User INTERFACE Testing

First they will conduct

SET _window is used to set a particular window, where if we want to work with the window that window has to be changed from RESET STATE to set state.

Win_active is used LIKE a window is already OPENED to activate the window which is on the status bar.

Set _window is used to set a particular window, where if we want to work with the window that window has to be changed from reset state to set state.

Win_active is used like a window is already opened to activate the window which is on the status bar.

GUI map is used to RECOGNIZE OBJECT's in our APPLICATION.

GUI map is used to recognize object's in our application.

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.

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.

The PROCESS to test the Pocket PC as follows:

1.  Go through the specifications well and understand it.
2.  As we are BLACKBOX testers and WinRunner helps US in doing Functional and Regression Testing.
3.  Understand the FUNCTIONALITY of the application.
4.  Start generating script for checking the BEHAVIOR of the application.

The process to test the Pocket PC as follows:

It CONTAINS the statement in Mercury INTERACTIVE Test Script Language (TSL). These statements appear as a test script in a test window. You can then enhance your recorded test script, either by typing in additional TSL functions and programming elements or by USING WinRunners VISUAL programming TOOL, the Function Generator.

It contains the statement in Mercury Interactive Test Script Language (TSL). These statements appear as a test script in a test window. You can then enhance your recorded test script, either by typing in additional TSL functions and programming elements or by using WinRunners visual programming tool, the Function Generator.

Entry CRITERIA: sign off proposal DOCUMENT by the client.
Exit criteria: sign off of TEST PLAN document by the client (test STRATEGY document).

Entry criteria: sign off proposal document by the client.
Exit criteria: sign off of test plan document by the client (test strategy document).

WINRUNNER is not support to XML. QTP is supported to XML. In QTP TWO TYPES of checkpoints are there one is web Xml checkpoint, DOCUMENT checkpoint.

Winrunner is not support to XML. QTP is supported to XML. In QTP two types of checkpoints are there one is web Xml checkpoint, document checkpoint.

In winrunner we can use REGULAR expression by doing UPDATION in the GUI MAP EDITOR by ADDING *, $, etc..

In winrunner we can use regular expression by doing updation in the GUI MAP EDITOR by adding *, $, etc..

• A TSL exception enables you to detect and respond to a specific error code RETURNED during TEST execution.
•  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.
•  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.
•  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.