Winrunner Testing Interview

1. What is the use of function generator? - a) The Function Generator provides a quick, error-free way to program scripts. You can:
   i. Add Context Sensitive functions that perform operations on a GUI object or get information from the application being tested.
   ii. Add Standard and Analog functions that perform non-Context Sensitive tasks such as synchronizing test execution or sending user-defined messages to a report.
   iii. Add Customization functions that enable you to modify WinRunner to suit your testing environment.
2. What is the use of putting call and call_close statements in the test script? - a) You can use two types of call statements to invoke one test from another:
   i. A call statement invokes a test from within another test.
   ii. A call_close statement invokes a test from within a script and closes the test when the test is completed.
   iii. The call statement has the following syntax:
3. call test_name ( [ parameter1, parameter2, ...parametern ] ); - iv. The call_close statement has the following syntax:
4. call_close test_name ( [ parameter1, parameter2, ... parametern ] ); - v. The test_name is the name of the test to invoke. The parameters are the parameters defined for the called test.
   vi. The parameters are optional. However, when one test calls another, the call statement should designate a value for each parameter defined for the called test. If no parameters are defined for the called test, the call statement must contain an empty set of parentheses.
5. What is the use of treturn and texit statements in the test script? - a) The treturn and texit statements are used to stop execution of called tests.
   i. The treturn statement stops the current test and returns control to the calling test.
   ii. The texit statement stops test execution entirely, unless tests are being called from a batch test. In this case, control is returned to the main batch test.
   b) Both functions provide a return value for the called test. If treturn or texit is not used, or if no value is specified, then the return value of the call statement is 0.
   treturn
   c) The treturn statement terminates execution of the called test and returns control to the calling test.
   The syntax is:
   treturn [( expression )];
   d) The optional expression is the value returned to the call statement used to invoke the test.
   texit
   e) When tests are run interactively, the texit statement discontinues test execution. However, when tests are called from a batch test, texit ends execution of the current test only; control is then returned to the calling batch test.
   The syntax is:
   texit [( expression )];
6. Where do you set up the search path for a called test. - a) The search path determines the directories that WinRunner will search for a called test.
   b) To set the search path, choose Settings > General Options. The General Options dialog box opens. Click the Folders tab and choose a search path in the Search Path for Called Tests box. WinRunner searches the directories in the order in which they are listed in the box. Note that the search paths you define remain active in future testing sessions.
7. How you create user-defined functions and explain the syntax? - a) A user-defined function has the following structure:
   [class] function name ([mode] parameter…)
   {
   declarations;
   statements;
   }
   b) The class of a function can be either static or public. A static function is available only to the test or module within which the function was defined.
   c) Parameters need not be explicitly declared. They can be of mode in, out, or inout. For all non-array parameters, the default mode is in. For array parameters, the default is inout. The significance of each of these parameter types is as follows:
   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.
8. What does static and public class of a function means? - a) The class of a function can be either static or public.
   b) A static function is available only to the test or module within which the function was defined.
   c) Once you execute a public function, it is available to all tests, for as long as the test containing the function remains open. This is convenient when you want the function to be accessible from called tests. However, if you want to create a function that will be available to many tests, you should place it in a compiled module. The functions in a compiled module are available for the duration of the testing session.
   d) If no class is explicitly declared, the function is assigned the default class, public.
9. What does in, out and input parameters means? - a) in: A parameter that is assigned a value from outside the function.
   b) out: A parameter that is assigned a value from inside the function.
   c) inout: A parameter that can be assigned a value from outside or inside the function.
10. What is the purpose of return statement? - a) This statement passes control back to the calling function or test. It also returns the value of the evaluated expression to the calling function or test. If no expression is assigned to the return statement, an empty string is returned.
    Syntax: return [( expression )];
11. What does auto, static, public and extern variables means? - a) 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.
    b) 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.
    c) public: A public variable can be declared only within a test or module, and is available for all functions, tests, and compiled modules.
    d) extern: An extern declaration indicates a reference to a public variable declared outside of the current test or module.
12. How do you declare constants? - a) The const specifier indicates that the declared value cannot be modified. The class of a constant may be either public or static. If no class is explicitly declared, the constant is assigned the default class public. Once a constant is defined, it remains in existence until you exit WinRunner.
    b) The syntax of this declaration is:
    [class] const name [= expression];
13. How do you declare arrays? - a) The following syntax is used to define the class and the initial expression of an array. Array size need not be defined in TSL.
    b) class array_name [ ] [=init_expression]
    c) The array class may be any of the classes used for variable declarations (auto, static, public, extern).
14. How do you load and unload a compile module? - a) In order to access the functions in a compiled module you need to load the module. You can load it from within any test script using the load command; all tests will then be able to access the function until you quit WinRunner or unload the compiled module.
    b) You can load a module either as a system module or as a user module. A system module is generally a closed module that is “invisible” to the tester. It is not displayed when it is loaded, cannot be stepped into, and is not stopped by a pause command. A system module is not unloaded when you execute an unload statement with no parameters (global unload).
    load (module_name [,1|0] [,1|0] );
    The module_name is the name of an existing compiled module. Two additional, optional parameters indicate the type of module. The first parameter indicates whether the function module is a system module or a user module: 1 indicates a system module; 0 indicates a user module.
    (Default = 0)
    The second optional parameter indicates whether a user module will remain open in the WinRunner window or will close automatically after it is loaded: 1 indicates that the module will close automatically; 0 indicates that the module will remain open.
    (Default = 0)
    c) The unload function removes a loaded module or selected functions from memory.
    d) It has the following syntax:
    unload ( [ module_name | test_name [ , "function_name" ] ] );
15. How do you update your expected results? -
16. How do you run your script with multiple sets of expected results? -
17. How do you view and evaluate test results for various check points? -
18. How do you view the results of file comparison? -
19. What is the purpose of Wdiff utility? -
20. What are batch tests and how do you create and run batch tests ? -
21. How do you store and view batch test results? -
22. How do you execute your tests from windows run command? -
23. Explain different command line options? -
24. What TSL function you will use to pause your script? -
25. What is the purpose of setting a break point? -
26. What is a watch list? -
27. During debugging how do you monitor the value of the variables? -
28. What are the reasons that WinRunner fails to identify an object on the GUI? - a) 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.
29. What do you mean by the logical name of the object. - a) An object’s logical name is determined by its class. In most cases, the logical name is the label that appears on an object.
30. If the object does not have a name then what will be the logical name? - If the object does not have a name then the logical name could be the attached text.
31. What is the different between GUI map and GUI map files? - a) 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.
    b) 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.
32. How do you view the contents of the GUI map? - a) 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.
33. What is startup script in WinRunner? - It is writing a script and when WinRunner starts it automatically runs the script. If you write script like invoking some application as soon as the script is run the application will be invoked for the purpose of testing
34. What is the purpose of loading WinRunner add-ins? - 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
35. What is the purpose of GUI spy? - Using the GUI spy you can view the properties of any GUI object and your desktop. You use the spy pointer to point to an object,and the GUI spy displays the properties and their values in the GUI spy dialog box. You can choose to view all properties of an object, or only the selected set of properties that WinRunner learns.
36. When you create GUI map do you record all the objects of specific objects? - a) 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.
37. What is the purpose of set_window command? - b) 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.
38. How do you load GUI map? - c) We can load a GUI Map by using the GUI_load command. Syntax: GUI_load();
39. What is the disadvantage of loading the GUI maps through start up scripts? - d) 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. e) 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.
40. How do you unload the GUI map? - f) 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;

Winrunner interview

1. What are the virtual objects and how do you learn them? - a) Applications may contain bitmaps that look and behave like GUI objects. WinRunner records operations on these bitmaps using win_mouse_click statements. By defining a bitmap as a virtual object, you can instruct WinRunner to treat it like a GUI object such as a push button, when you record and run tests.
   b) Using the Virtual Object wizard, you can assign a bitmap to a standard object class, define the coordinates of that object, and assign it a logical name.
   To define a virtual object using the Virtual Object wizard:
   i. Choose Tools > Virtual Object Wizard. The Virtual Object wizard opens. Click Next.
   ii. In the Class list, select a class for the new virtual object. If rows that are displayed in the window. For a table class, select the number of visible rows and columns. Click Next.
   iii. Click Mark Object. Use the crosshairs pointer to select the area of the virtual object. You can use the arrow keys to make precise adjustments to the area you define with the crosshairs. Press Enter or click the right mouse button to display the virtual object’s coordinates in the wizard. If the object marked is visible on the screen, you can click the Highlight button to view it. Click Next.
   iv.Assign a logical name to the virtual object. This is the name that appears in the test script when you record on the virtual object. If the object contains text that WinRunner can read, the wizard suggests using this text for the logical name. Otherwise, WinRunner suggests virtual_object, virtual_push_button, virtual_list, etc.
   v. You can accept the wizard’s suggestion or type in a different name. WinRunner checks that there are no other objects in the GUI map with the same name before confirming your choice. Click Next.
2. H ow you created you test scripts 1) by recording or 2) programming? - a) Programming. I have done complete programming only, absolutely no recording.
3. 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.
4. 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.
5. 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.
6. 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.
7. 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 );
8. 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:
9. 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. -
10. Click an object. -
11. 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.
12. 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. -
13. 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. -
14. To change the viewing options for the properties of an object, use the Show Properties buttons. -
15. 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 );

Winrunner Interview questions and answers

1. How do you analyze results and report the defects? - a) 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.
2. What are the different modes of recording? - a) 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.
3. What is the purpose of loading WinRunner Add-Ins? - a) 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.
4. How to modify the logical name or physical description of the object? - Using GUI editor
5. How Winrunner handles varying window labels? - Using regular expressions
6. How do you write messages to the report? - report_msg
7. How you used WinRunner in your project? - Yes, I have been WinRunner for creating automates scripts for GUI, functional and regression testing of the AUT.
8. Explain WinRunner testing process? - 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.
   iiiDebug 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.
9. What in contained in the GUI map? - a) 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.
   b) 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.
10. How does WinRunner recognize objects on the application? - a)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 anobject’sdescription in the GUI map and then looks for an object with the same properties in the application being tested.
11. Have you created test scripts and what is contained in the test scripts? - a) 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.
12. How does WinRunner evaluates test results? - a) 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.
13. Have you performed debugging of the scripts? - a) 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.
14. How do you view the contents of the GUI map? - a) 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.
15. When you create GUI map do you record all the objects of specific objects? - a) 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.
16. What is the purpose of set_window command? - a) 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.
17. How do you load GUI map? - a) We can load a GUI Map by using the GUI_load command.
    Syntax: GUI_load();
18. What is the disadvantage of loading the GUI maps through start up scripts? - 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.
19. How do you unload the GUI map? - a) 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;
20. What actually happens when you load GUI map? - a) 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.
21. What is the purpose of the temp GUI map file? - a) 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.
22. What is the extension of gui map file? - a) The extension for a GUI Map file is “.gui�.
23. How do you find an object in an GUI map. - a) 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.
24. What different actions are performed by find and show button? - a) 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.
    b) 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.
25. How do you identify which files are loaded in the GUI map? - a) The GUI Map Editor has a drop down “GUI File� displaying all the GUI Map files loaded into the memory.
26. How do you modify the logical name or the physical description of the objects in GUI map? - a) You can modify the logical name or the physical description of an object in a GUI map file using the GUI Map Editor.
27. When do you feel you need to modify the logical name? - a) Changing the logical name of an object is useful when the assigned logical name is not sufficiently descriptive or is too long.
28. When it is appropriate to change physical description? - a) Changing the physical description is necessary when the property value of an object changes.
29. How WinRunner handles varying window labels? - a) 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.
30. What is the purpose of regexp_label property and regexp_MSW_class property? - a) 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.
    b) 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.
31. How do you suppress a regular expression? - a) We can suppress the regular expression of a window by replacing the regexp_label property with label property.
32. How do you copy and move objects between different GUI map files? - a) We can copy and move objects between different GUI Map 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.
33. How do you select multiple objects during merging the files? - a) 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.
34. How do you clear a GUI map files? - a) We can clear a GUI Map file using the “Clear All� option in the GUI Map Editor.
35. How do you filter the objects in the GUI map? - a) 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.
36. How do you configure gui map? - 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 classes. 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.
37. W hat is the purpose of GUI map configuration? - a) GUI Map configuration is used to map a custom object to a standard object.
38. How do you make the configuration and mappings permanent? - a) 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.
39. What is the purpose of GUI spy? - a) Using the GUI Spy, you can view the properties of any GUI object on your desktop. You use the Spy pointer to point to an object, and the GUI Spy displays the properties and their values in the GUI Spy dialog box. You can choose to view all the properties of an object, or only the selected set of properties that WinRunner learns.
40. What is the purpose of obligatory and optional properties of the objects? - a) For each class, WinRunner learns a set of default properties. Each default property is classified “obligatory� or “optional�.
    i. An obligatory property is always learned (if it exists).
    ii.An optional property is used only if the obligatory properties do not provide unique identification of an object. These optional properties are stored in a list. WinRunner selects the minimum number of properties from this list that are necessary to identify the object. It begins with the first property in the list, and continues, if necessary, to add properties to the description until it obtains unique identification for the object.
41. When the optional properties are learned? - a) An optional property is used only if the obligatory properties do not provide unique identification of an object.
42. What is the purpose of location indicator and index indicator in GUI map configuration? - a) 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:
    i. A location selector uses the spatial position of objects.
43. The location selector uses the spatial order of objects within the window, from the top left to the bottom right corners, to differentiate among objects with the same description. - ii. An index selector uses a unique number to identify the object in a window.
44. The index selector uses numbers assigned at the time of creation of objects to identify the object in a window. Use this selector if the location of objects with the same description may change within a window. -
45. How do you handle custom objects? - a) A custom object is any GUI object not belonging to one of the standard classes used by WinRunner. WinRunner learns such objects under the generic “object� class. WinRunner records operations on custom objects using obj_mouse_ statements.
    b) If a custom object is similar to a standard object, you can map it to one of the standard classes. You can also configure the properties WinRunner uses to identify a custom object during Context Sensitive testing.
46. What is the name of custom class in WinRunner and what methods it applies on the custom objects? - a) WinRunner learns custom class objects under the generic “object� class. WinRunner records operations on custom objects using obj_ statements.
47. In a situation when obligatory and optional both the properties cannot uniquely identify an object what method WinRunner applies? - a) 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:
    i. A location selector uses the spatial position of objects.
    ii. An index selector uses a unique number to identify the object in a window.
    63 What is the purpose of different record methods 1) Record 2) Pass up 3) As Object 4) Ignore.
    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.
48. How do you find out which is the start up file in WinRunner? - a) The test script name in the Startup Test box in the Environment tab in the General Options dialog box is the start up file in WinRunner.

Debugging winrunner Script?

Debugging winrunner Script?
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.

How does WinRunner evaluates test results?

How does WinRunner evaluates test results?
a) 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. 

what is contained in the test scripts? ----Winrunner

what is contained in the test scripts? ----Winrunner Interview Questions
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.

How does WinRunner recognize objects on the application?

How does WinRunner recognize objects on the application?--Winrunner interview
a) 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. 

What is contained in the GUI map?--Winrunner

What is contained in the GUI map?--Winrunner interview question
a) 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.
b) 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.