Explore topic-wise InterviewSolutions in .

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:

1. 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.
2. Bitmap checkpoints take a snapshot of a window or area of your application and compare this to an IMAGE captured in an earlier version.
3. Text checkpoints read text in GUI objects and in bitmaps and enable you to verify their CONTENTS.
4. 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.

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:

There are 2 modes of recording in WinRunner
• Context Sensitive recording records the OPERATIONS you PERFORM on your application by identifying Graphical User Interface (GUI) objects.
• Analog recording records keyboard input, mouse clicks, and the precise x- and y-coordinates traveled by the mouse POINTER across the SCREEN.

There are 2 modes of recording in WinRunner
• Context Sensitive recording records the operations you perform on your application by identifying Graphical User Interface (GUI) objects.
• Analog recording records keyboard input, mouse clicks, and the precise x- and y-coordinates traveled by the mouse pointer across the screen.

a) Record INSTRUCTS WinRunner to record all OPERATIONS performed on a GUI object. This is the DEFAULT record method for all classes. (The only exception is the STATIC class (static text), for which the default is Pass Up.)
b) Pass Up instructs WinRunner to record an operation performed on this class as an operation performed on the element containing the object. Usually this element is a window, and the operation is RECORDED as win_mouse_click.
c) As Object instructs WinRunner to record all operations performed on a GUI object as though its class were “object” class.
d) Ignore instructs WinRunner to disregard all operations performed on the class.

a) Record instructs WinRunner to record all operations performed on a GUI object. This is the default record method for all classes. (The only exception is the static class (static text), for which the default is Pass Up.)
b) Pass Up instructs WinRunner to record an operation performed on this class as an operation performed on the element containing the object. Usually this element is a window, and the operation is recorded as win_mouse_click.
c) As Object instructs WinRunner to record all operations performed on a GUI object as though its class were “object” class.
d) Ignore instructs WinRunner to disregard all operations performed on the class.

a) If we are USING a single GUI Map file for the ENTIRE AUT then the memory used by the GUI Map may be MUCH high.
b) If there is any change in the object being learned then WinRunner will not be able to recognize the object, as it is not in the GUI Map file LOADED in the memory. So we will have to learn the object again and update the GUI File and reload it.

a) If we are using a single GUI Map file for the entire AUT then the memory used by the GUI Map may be much high.
b) If there is any change in the object being learned then WinRunner will not be able to recognize the object, as it is not in the GUI Map file loaded in the memory. So we will have to learn the object again and update the GUI File and reload it.

“WinRunner handles automation TEST SCRIPTS
TESTDIRECTOR MANAGES test scripts, defects and test PLAN”

“WinRunner handles automation test scripts
TestDirector manages test scripts, defects and test plan”

“TEST SCRIPT LANGUAGE, TSL C++”

“Test Script Language, TSL C++”

ORACLE, ACCESS, SYBASE, MSSQL

Oracle, Access, Sybase, MsSQL

Data is WRITTEN MULTIPLE TIMES, while WinRunner has a repeated LOOP to process the data.

Data is written multiple times, while WinRunner has a repeated loop to process the data.

USED to COORDINATE and MANAGE TEST CASES.

Used to coordinate and manage test cases.

LOAD or RELOAD FUNCTION

Load or Reload function

CONFIGURATION SET up for WINRUNNER

Configuration set up for WinRunner

a. When WinRunner learns the description of a GUI object, it does not learn all its properties. Instead, it learns the minimum number of properties to PROVIDE a unique identification of the object.
b. Many applications ALSO contain custom GUI OBJECTS. A custom object is any object not belonging to one of the standard classes used by WinRunner. These objects are therefore assigned to the generic “object” class. When WinRunner records an OPERATION on a custom object, it generates obj_mouse_ statements in the test script.
c. If a custom object is similar to a standard object, you can map it to one of the standard . You can also configure the properties WinRunner uses to identify a custom object during Context Sensitive testing. 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.

a. When WinRunner learns the description of a GUI object, it does not learn all its properties. Instead, it learns the minimum number of properties to provide a unique identification of the object.
b. Many applications also contain custom GUI objects. A custom object is any object not belonging to one of the standard classes used by WinRunner. These objects are therefore assigned to the generic “object” class. When WinRunner records an operation on a custom object, it generates obj_mouse_ statements in the test script.
c. If a custom object is similar to a standard object, you can map it to one of the standard . You can also configure the properties WinRunner uses to identify a custom object during Context Sensitive testing. 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.

GUI Map Editor has a Filter option. This provides for filtering with 3 different types of options.
i. LOGICAL name displays only objects with the specified logical name.
ii. Physical DESCRIPTION displays only objects matching the specified physical description. Use any substring BELONGING to the physical description.
iii. Class displays only objects of the specified class, such as all the push buttons.

GUI Map Editor has a Filter option. This provides for filtering with 3 different types of options.
i. Logical name displays only objects with the specified logical name.
ii. Physical description displays only objects matching the specified physical description. Use any substring belonging to the physical description.
iii. Class displays only objects of the specified class, such as all the push buttons.

We can clear a GUI Map FILE USING the “Clear All” option in the GUI Map Editor.

We can clear a GUI Map file using the “Clear All” option in the GUI Map Editor.

Use the Shift key and/or CONTROL key to SELECT multiple objects. To select all objects in a GUI map file, CHOOSE EDIT > Select All.

Use the Shift key and/or Control key to select multiple objects. To select all objects in a GUI map file, choose Edit > Select All.

We can copy and move objects between different GUI FILES using the GUI Map Editor. The steps to be followed are: i. Choose Tools > GUI Map Editor to open the GUI Map Editor.
II. Choose View > GUI Files.
III. Click Expand in the GUI Map Editor. The dialog box expands to display two GUI map files simultaneously.
iv. View a different GUI map file on each side of the dialog box by clicking the file NAMES in the GUI File lists.
v. In one file, select the objects you want to copy or move. Use the Shift key and/or Control key to select multiple objects. To select all objects in a GUI map file, choose Edit > Select All.
VI. Click Copy or Move.
vii. To restore the GUI Map Editor to its original size, click Collapse.

We can copy and move objects between different GUI files using the GUI Map Editor. The steps to be followed are: i. Choose Tools > GUI Map Editor to open the GUI Map Editor.
ii. Choose View > GUI Files.
iii. Click Expand in the GUI Map Editor. The dialog box expands to display two GUI map files simultaneously.
iv. View a different GUI map file on each side of the dialog box by clicking the file names in the GUI File lists.
v. In one file, select the objects you want to copy or move. Use the Shift key and/or Control key to select multiple objects. To select all objects in a GUI map file, choose Edit > Select All.
vi. Click Copy or Move.
vii. To restore the GUI Map Editor to its original size, click Collapse.

We can SUPPRESS the regular expression of a WINDOW by REPLACING the regexp_label PROPERTY with LABEL property.

We can suppress the regular expression of a window by replacing the regexp_label property with label property.

The regexp_label property is used for windows only. It operates “BEHIND the scenes” to insert a REGULAR EXPRESSION into a window’s label description.
The regexp_MSW_class property inserts a regular expression into an object’s MSW_class. It is OBLIGATORY for all TYPES of windows and for the object class object.

The regexp_label property is used for windows only. It operates “behind the scenes” to insert a regular expression into a window’s label description.
The regexp_MSW_class property inserts a regular expression into an object’s MSW_class. It is obligatory for all types of windows and for the object class object.

We can handle varying window labels using regular expressions. WinRunner uses two “HIDDEN” properties in order to use regular expression in an object’s physical description. These properties are regexp_label and regexp_MSW_class.
i. The regexp_label property is USED for windows only. It operates “behind the SCENES” to insert a regular expression into a window’s label description.
ii. The regexp_MSW_class property inserts a regular expression into an object’s MSW_class. It is obligatory for all types of windows and for the object class object.

We can handle varying window labels using regular expressions. WinRunner uses two “hidden” properties in order to use regular expression in an object’s physical description. These properties are regexp_label and regexp_MSW_class.
i. The regexp_label property is used for windows only. It operates “behind the scenes” to insert a regular expression into a window’s label description.
ii. The regexp_MSW_class property inserts a regular expression into an object’s MSW_class. It is obligatory for all types of windows and for the object class object.

CHANGING the PHYSICAL DESCRIPTION is NECESSARY when the property value of an object changes.

Changing the physical description is necessary when the property value of an object changes.

CHANGING the logical NAME of an OBJECT is useful when the ASSIGNED logical name is not sufficiently descriptive or is too long.

Changing the logical name of an object is useful when the assigned logical name is not sufficiently descriptive or is too long.

You can modify the LOGICAL name or the PHYSICAL DESCRIPTION of an object in a GUI map file using the GUI Map EDITOR.

You can modify the logical name or the physical description of an object in a GUI map file using the GUI Map Editor.

The GUI MAP Editor has a drop down “GUI FILE” DISPLAYING all the GUI Map files loaded into the memory.

The GUI Map Editor has a drop down “GUI File” displaying all the GUI Map files loaded into the memory.

1.To FIND a particular OBJECT in the GUI Map file in the application, select the object and click the SHOW window. This blinks the selected object.
2.To find a particular object in a GUI Map file click the Find button, which gives the option to select the object. When the object is selected, if the object has been learned to the GUI Map file it will be FOCUSED in the GUI Map file.

1.To find a particular object in the GUI Map file in the application, select the object and click the Show window. This blinks the selected object.
2.To find a particular object in a GUI Map file click the Find button, which gives the option to select the object. When the object is selected, if the object has been learned to the GUI Map file it will be focused in the GUI Map file.

The GUI Map Editor is been provided with a Find and Show Buttons.
i. To find a particular object in the GUI Map FILE in the application, select the object and CLICK the Show WINDOW. This blinks the selected object.
ii. To find a particular object in a GUI Map file click the Find button, which gives the OPTION to select the object. When the object is selected, if the object has been LEARNED to the GUI Map file it will be focused in the GUI Map file.

The GUI Map Editor is been provided with a Find and Show Buttons.
i. To find a particular object in the GUI Map file in the application, select the object and click the Show window. This blinks the selected object.
ii. To find a particular object in a GUI Map file click the Find button, which gives the option to select the object. When the object is selected, if the object has been learned to the GUI Map file it will be focused in the GUI Map file.

The EXTENSION for a GUI MAP FILE is “.gui”.

The extension for a GUI Map file is “.gui”.

While recording a script, WinRunner learns OBJECTS and windows by itself. This is actually stored into the temporary GUI Map file. We can specify whether we have to load this temporary GUI Map file should be LOADED each time in the GENERAL Options.

While recording a script, WinRunner learns objects and windows by itself. This is actually stored into the temporary GUI Map file. We can specify whether we have to load this temporary GUI Map file should be loaded each time in the General Options.

When we load a GUI Map file, the INFORMATION about the WINDOWS and the OBJECTS with their logical names and physical DESCRIPTION are loaded into memory. So when the WinRunner executes a script on a particular window, it can identify the objects using this information loaded in the memory.

When we load a GUI Map file, the information about the windows and the objects with their logical names and physical description are loaded into memory. So when the WinRunner executes a script on a particular window, it can identify the objects using this information loaded in the memory.

We can use GUI_close to UNLOAD a specific GUI Map FILE or else we CALL use GUI_close_all command to unload all the GUI Map files loaded in the memory.
Syntax: GUI_close(); or GUI_close_all;

We can use GUI_close to unload a specific GUI Map file or else we call use GUI_close_all command to unload all the GUI Map files loaded in the memory.
Syntax: GUI_close(); or GUI_close_all;

1.If we are using a single GUI Map FILE for the ENTIRE AUT then the MEMORY used by the GUI Map may be much high.
2.If there is any change in the OBJECT being learned then WinRunner will not be able to recognize the object, as it is not in the GUI Map file loaded in the memory. So we will have to learn the object again and update the GUI File and reload it.

1.If we are using a single GUI Map file for the entire AUT then the memory used by the GUI Map may be much high.
2.If there is any change in the object being learned then WinRunner will not be able to recognize the object, as it is not in the GUI Map file loaded in the memory. So we will have to learn the object again and update the GUI File and reload it.

We can load a GUI MAP by USING the GUI_load COMMAND.
SYNTAX: GUI_load();

We can load a GUI Map by using the GUI_load command.
Syntax: GUI_load();

Set_Window command sets the focus to the specified window. We use this command to SET the focus to the required window before executing TESTS on a particular window.
Syntax: set_window(, time); The logical NAME is the logical name of the window and time is the time the EXECUTION has to wait TILL it gets the given window into focus.

Set_Window command sets the focus to the specified window. We use this command to set the focus to the required window before executing tests on a particular window.
Syntax: set_window(, time); The logical name is the logical name of the window and time is the time the execution has to wait till it gets the given window into focus.

If we are LEARNING a window then WinRunner automatically learns all the objects in the window else we will we identifying those OBJECT, which are to be learned in a window, since we will be WORKING with only those objects while creating SCRIPTS.

If we are learning a window then WinRunner automatically learns all the objects in the window else we will we identifying those object, which are to be learned in a window, since we will be working with only those objects while creating scripts.

GUI Map EDITOR DISPLAYS the content of a GUI Map. We can INVOKE GUI Map Editor from the Tools MENU in WinRunner. The GUI Map Editor displays the various GUI Map files CREATED and the windows and objects learned in to them with their logical name and physical description.

GUI Map editor displays the content of a GUI Map. We can invoke GUI Map Editor from the Tools Menu in WinRunner. The GUI Map Editor displays the various GUI Map files created and the windows and objects learned in to them with their logical name and physical description.

The GUI MAP is actually the sum of one or more GUI map FILES. There are two modes for organizing GUI map files.
i. Global GUI Map file: a single GUI Map file for the entire application
II. GUI Map File per Test: WinRunner automatically creates a GUI Map file for each test created. GUI Map file is a file which contains the windows and the objects LEARNED by the WinRunner with its LOGICAL name and their physical description.

The GUI map is actually the sum of one or more GUI map files. There are two modes for organizing GUI map files.
i. Global GUI Map file: a single GUI Map file for the entire application
ii. GUI Map File per Test: WinRunner automatically creates a GUI Map file for each test created. GUI Map file is a file which contains the windows and the objects learned by the WinRunner with its logical name and their physical description.

If the OBJECT does not have a name then the LOGICAL name could be the ATTACHED TEXT.

If the object does not have a name then the logical name could be the attached text.

An OBJECT’s LOGICAL name is determined by its class. In most CASES, the logical name is the label that APPEARS on an object.

An object’s logical name is determined by its class. In most cases, the logical name is the label that appears on an object.

WinRunner FAILS to identify an object in a GUI due to various REASONS.
i. The object is not a standard windows object.
ii. If the browser used is not compatible with the WinRunner VERSION, GUI MAP Editor will not be able to learn any of the objects displayed in the browser window.

WinRunner fails to identify an object in a GUI due to various reasons.
i. The object is not a standard windows object.
ii. If the browser used is not compatible with the WinRunner version, GUI Map Editor will not be able to learn any of the objects displayed in the browser window.

Add-Ins are used in WinRunner to load functions specific to the particular add-in to the MEMORY. While creating a script only those functions in the add-in SELECTED will be LISTED in the function generator and while executing the script only those functions in the loaded add-in will be executed else WinRunner will GIVE an error message SAYING it does not recognize the function.

Add-Ins are used in WinRunner to load functions specific to the particular add-in to the memory. While creating a script only those functions in the add-in selected will be listed in the function generator and while executing the script only those functions in the loaded add-in will be executed else WinRunner will give an error message saying it does not recognize the function.

There are two type 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.

There are two type 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.

When you work with WINRUNNER, you can choose to save your TESTS DIRECTLY to your TestDirector database or while creating a TEST case in the TestDirector we can specify whether the script in automated or manual. And if it is automated script then TestDirector will build a skeleton for the script that can be later MODIFIED into one which could be used to test the AUT.

When you work with WinRunner, you can choose to save your tests directly to your TestDirector database or while creating a test case in the TestDirector we can specify whether the script in automated or manual. And if it is automated script then TestDirector will build a skeleton for the script that can be later modified into one which could be used to test the AUT.

Following each TEST run, WinRunner displays the results in a report. The report details all the major events that occurred during the run, such as checkpoints, ERROR messages, system messages, or USER messages. If mismatches are detected at checkpoints during the test run, you can view the expected results and the actual results from the Test Results window. If a test run fails DUE to a defect in the application being tested, you can report information about the defect DIRECTLY from the Test Results window. This information is sent via e-mail to the quality assurance manager, who tracks the defect until it is fixed.

Following each test run, WinRunner displays the results in a report. The report details all the major events that occurred during the run, such as checkpoints, error messages, system messages, or user messages. If mismatches are detected at checkpoints during the test run, you can view the expected results and the actual results from the Test Results window. If a test run fails due to a defect in the application being tested, you can report information about the defect directly from the Test Results window. This information is sent via e-mail to the quality assurance manager, who tracks the defect until it is fixed.

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

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

Yes, I have performed debugging of scripts. We can DEBUG the script by EXECUTING the script in the debug MODE. We can also debug script using the Step, Step Into, Step out functionalities PROVIDED by the WINRUNNER.

Yes, I have performed debugging of scripts. We can debug the script by executing the script in the debug mode. We can also debug script using the Step, Step Into, Step out functionalities provided by the WinRunner.

Following each test RUN, WinRunner DISPLAYS the results in a report. The report details all the MAJOR EVENTS that occurred during the run, such as checkpoints, error messages, system messages, or user messages. If mismatches are detected at checkpoints during the test run, you can view the expected results and the actual results from the Test Results WINDOW.

Following each test run, WinRunner displays the results in a report. The report details all the major events that occurred during the run, such as checkpoints, error messages, system messages, or user messages. If mismatches are detected at checkpoints during the test run, you can view the expected results and the actual results from the Test Results window.

Yes I have created test scripts. It contains the statement in Mercury Interactive’s 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 WinRunner’s visual programming tool, the Function Generator.

Yes I have created test scripts. It contains the statement in Mercury Interactive’s 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 WinRunner’s visual programming tool, the Function Generator.

WINRUNNER uses the GUI MAP file to recognize OBJECTS on the application. When WinRunner runs a test, it uses the GUI map to LOCATE objects. It reads an object’s description in the GUI map and then looks for an object with the same properties in the application being TESTED.

WinRunner uses the GUI Map file to recognize objects on the application. When WinRunner runs a test, it uses the GUI map to locate objects. It reads an object’s description in the GUI map and then looks for an object with the same properties in the application being tested.

WinRunner stores information it learns about a window or OBJECT in a GUI Map. When WinRunner RUNS a test, it uses the GUI map to locate OBJECTS. It reads an object’s description in the GUI map and then looks for an object with the same properties in the application being tested. Each of these objects in the GUI Map file will be having a LOGICAL name and a physical description. There are 2 types of GUI Map files.
i. Global GUI Map file: a single GUI Map file for the entire application
ii. GUI Map File per Test: WinRunner AUTOMATICALLY creates a GUI Map file for each test created.

WinRunner stores information it learns about a window or object in a GUI Map. When WinRunner runs a test, it uses the GUI map to locate objects. It reads an object’s description in the GUI map and then looks for an object with the same properties in the application being tested. Each of these objects in the GUI Map file will be having a logical name and a physical description. There are 2 types of GUI Map files.
i. Global GUI Map file: a single GUI Map file for the entire application
ii. GUI Map File per Test: WinRunner automatically creates a GUI Map file for each test created.

WinRunner testing process involves six MAIN stages:
i. Create GUI Map File so that WinRunner can recognize the GUI objects in the application being tested
II. Create test scripts by recording, programming, or a combination of both. While recording tests, insert checkpoints where you WANT to check the response of the application being tested.
iii. Debug Test: run tests in Debug mode to MAKE sure they run smoothly
iv. Run Tests: run tests in Verify mode to test your application.
v. View RESULTS: determines the success or failure of the tests.
vi. Report Defects: If a test run fails due to a defect in the application being tested, you can report information about the defect directly from the Test Results window.

WinRunner testing process involves six main stages:
i. Create GUI Map File so that WinRunner can recognize the GUI objects in the application being tested
ii. Create test scripts by recording, programming, or a combination of both. While recording tests, insert checkpoints where you want to check the response of the application being tested.
iii. Debug Test: run tests in Debug mode to make sure they run smoothly
iv. Run Tests: run tests in Verify mode to test your application.
v. View Results: determines the success or failure of the tests.
vi. Report Defects: If a test run fails due to a defect in the application being tested, you can report information about the defect directly from the Test Results window.

Yes, I have been WinRunner for creating automates scripts for GUI, functional and REGRESSION TESTING of the AUT.

Yes, I have been WinRunner for creating automates scripts for GUI, functional and regression testing of the AUT.