Win Runner Interview Questions and Answers
Question - 81 : - Can parameters be added to database check points?
Answer - 81 : -
Parameters can be added to an SQL statement to parameterize a checkpoint using ODBC. This can be helpful in creating a database checkpoint with a query when the SQL statement that defines the query is expected to change.
Question - 82 : - Define compiled module?
Answer - 82 : -
A compiled module is a script that contains a library of functions defined by the user that will frequently be called from other tests. When a compiled module is loaded, the functions that it contains are compiled automatically and remain in memory. Using compiled modules can greatly improve test performance and organization because they are debugged before using so less error-checking is required. Also, calling a pre-compiled function is usually faster than interpreting one in a test script.
Question - 83 : - Explain the difference between a compile module and a script.
Answer - 83 : -
A compiled module is not executable and is used to store reusable functions while a test script contains the executable file. Compiled modules are loaded into memory and are referenced from the TSL code within a module.
Question - 84 : - Where is the search path set for calling a test?
Answer - 84 : -
The search path is used to set the directories that WinRunner will explore when searching for a test. This path is set in the Settings tab of the General options. Under Setting, there is a box labeled “Search Path for Called Tests” Several paths can be listed. WinRunner will search in the order that the directories are listed and the search paths defined are saved and active for future testing sessions.
Question - 85 : - What are the classes of a function?
Answer - 85 : -
There are two function classes: static and public. A static function is one that is only available in the test module where it is defined. Public functions on the other hand are available for all other tests once it is executed and as long as it is kept open. If it is desired to have a function available even when not opened, then the tester should consider using a compiled module. If a function definition does not declare a class, the default setting is public.
Question - 86 : - Why might WinRunner fail to identify an object on a GUI?
Answer - 86 : -
WinRunner might fail to recognize an object in a GUI if it is not a standard windows object or if the browser that is used is not compatible with the version of WinRunner that is being used for testing. In these cases, the GUI Map Editor may not be able to learn the objects.
Question - 87 : - How do you handle dynamically changing area of the window in the bitmap checkpoints?
Answer - 87 : -
The difference between bitmaps option in the Run Tab of the general options defines the minimum number of pixels that constitute a bitmap mismatch
Question - 88 : - What information is contained in the checklist file and in which file expected results are stored?
Answer - 88 : -
The checklist file contains information about the objects and the properties of the object we are verifying.
The gui*.chk file contains the expected results which is stored in the exp folder
Question - 89 : - What are the two modes of recording?
Answer - 89 : -
There are 2 modes of recording in WinRunner
1. Context Sensitive recording records the operations you perform on your application by identifying Graphical User Interface (GUI) objects.
2. Analog recording records keyboard input, mouse clicks, and the precise x- and y-coordinates traveled by the mouse pointer across the screen.
Question - 90 : - How do you find out which is the start up file in WinRunner?
Answer - 90 : -
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.