Win Runner Interview Questions and Answers
Question - 61 : - Why WinRunner fails to identify an object on the GUI?
Answer - 61 : -
WinRunner fails to identify an object in a GUI due to following reasons:
- When Physical and Logical name of object is not matching with the GUI object of the repository.
- The object is not a standard windows object.
- When browser is incompatible with the WinRunner version.
- When browser is incompatible it cannot add any object in the GUI MAP, which leads to fail to identifying object.
Question - 62 : - How to test Database using WinRunner?
Answer - 62 : -
We can test the database using WinRunner by the help of the Database checkpoints. These checkpoints can be inserted into the test script language (TSL) to examine the databases of application. By this we can easily trace out the defects which are present in the database. We can query on the database, to create a database checkpoint that evaluates the properties of the results of the query. There are two types of database checks can be done in WinRunner:
1. Default database check.
2. Custom database check.
Question - 63 : - When do you use Verify/Debug/Update Modes?
Answer - 63 : -
WinRunner provides three modes in which to run test:
Verify: Use to compares the actual result and expected response. If the actual result is different from the expected result then this is captured and saved as verification result.
Debug: Use the Debug mode to help you identify bugs in a test script. Verify mode and debug mode are same but the only differences between these two are debug results are always saved in the debug folder and only one set of debug results is stored.
Update mode: It is used when we want to update or change the expected result.
Question - 64 : - How do you manually capture an Object using WinRunner?
Answer - 64 : -
We can manually add an object to a GUI map file by copying the description of another object, and then editing it as needed. To manually add an object to a GUI map file. We follow the following steps:
- Choose Tools > GUI Map Editor to open the GUI Map Editor.
- Choose View > GUI Files.
- Choose File > Open to open the appropriate GUI map file.
- Select the object to use as the basis for editing.
- Click Add to open the Add dialog box.
Question - 65 : - What is a data driven test in WinRunner?
Answer - 65 : -
Data Driven is an automation testing part in which test input or output values, these values are read from data files. It is performed when the values are changing by the time. The different data files may include data pools, csv files, Excel files. The data is then loaded into variables in recorded or manually coded scripts. In WinRunner to use data to drive the test, we use the parameterization process. When we do data-driven test, we perform two extra steps:
- Converting the test to a data-driven test.
- Creating a corresponding data table.
Question - 66 : - How can you integrate your automated scripts from TestDirector?
Answer - 66 : -
In WinRunner, we can save tests directly to your TestDirector database. When creating a test case with the TestDirector we can declare that our script is automated or manual. When script is automated then TestDirector creates a skeleton for the script which can be modified. TestDirector stores test and defect information in a project. We can create TestDirector projects in Microsoft Access, Oracle, Sybase, or Microsoft SQL. These projects store information related to the current testing project, such as tests, test run results, and reported defects. To access the project connect it to the Web server where TestDirector is installed. When WinRunner is connected to TestDirector we can save a test by associating it with the Test Plan Manager.
Question - 67 : - What is the difference between GUI map and GUI map files?
Answer - 67 : -
The GUI map is group of one or more GUI map files. We can organize GUI map files in two ways:
- Global GUI Map file: a single GUI Map file for the entire application.
- 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 GUI Objects and windows learned by the WinRunner while recording the testing script with the logical name and physical properties of the objects.
Question - 68 : - What different actions are performed by find and show button?
Answer - 68 : -
The differences between show and find button are following:
- Show button is used to show the object for selected name whereas find button is used to find the name for selected object.
- Show Button to show a particular object in the application, select the object and click the Show window. This Highlight the selected object whereas
- Find button gives the option to select the object. When the object is selected, if the object is present in the GUI repository it will be focused in the file.
Question - 69 : - How does WinRunner handle varying window labels?
Answer - 69 : -
The Varying window labels problem can be solved by using the regular expressions. Regular expressions enable WinRunner to identify objects with varying names or titles. We can use regular expressions in Test Script Language statements. A regular expression is a string. Regular expression is followed by an exclamation mark. We use special characters such as a period (.), asterisk (*), caret (^), and brackets ([ ]), by this we can generate the conditions of the search. For example, the string “!hit.*” matches both “rohit” and “hit”.
Question - 70 : - Explain data parameterization in WinRunner.
Answer - 70 : -
It is the process of making use of different values in place of recorded values which is replaced by variable which contains different values that can be used during the execution of the scripts. It also reduces the size of the scripts. Parameterization is used when the values and the label of the window changes after every execution like we want to test the application in which order no is involved which is always incremented by 1. Then, in that case we use data parameterization.