-
How does WinRunner evaluates test results?
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.
-
-
-
-
-
How WinRunner handles varying window labels?
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...
-
-
-
-
-
What information is contained in the checklist file and in which file expected results are stored?
The checklist file contains information about the objects and the properties of the object we are verifying. b. The gui*.chk file contains the expected results which is stored in the exp folder
-
-
How do you handle custom objects?
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...
-
-
-
-
-
-
-
What is a compile module?
A compiled module is a script containing a library of user-defined functions that you want to call frequently from other tests. When you load a compiled module, its functions are automatically compiled and remain in memory. You can call them directly from within any test. b. Compiled modules can improve the organization and performance of your tests. Since you debug compiled modules before using...
Winrunner Interview Questions
Ans