Six main stages are involved in WinRunner testing process:
GUI Map File creation: By doing this we make GUI object available for the WinRunner test.
Generating Test Script: by recording, programming, or a combination of both.
Debugging Test: run tests in Debug mode to remove the errors in Test Script.
Run Tests: run tests in Verify mode to test application.
View Results: determines the status of test result, PASS or FAIL.
Report Defects: when status of test run is fail, then we can report information about the defect directly from the Test Results window.
How do you handle TSL exceptions?
Suppose you are running a batch test on an unstable version of your application. If your application crashes, you want WinRunner to recover test execution. A TSL exception can instruct WinRunner to recover test execution by exiting the current test, restarting the application, and continuing with the next test in the batch.
The handler function is responsible for recovering test execution. When WinRunner detects a specific error code, it calls the handler function. You implement this function to respond to the unexpected error in the way that meets your specific testing needs.
What is contained in the GUI map?
GUI Map File stores the element identification properties extracted from the application during recording. ID will be generated for each element and this ID is used for Object identification in the application. GUI Map file acts as a repository for the application elements. GUI Map file contains two properties of each object for the identification:
Physical name of the object :
Logical name of the object:
How do you handle pop-up exceptions?
A pop-up exception Handler handles the pop-up messages that come up during the execution of the script in the AUT. TO handle this type of exception we make WinRunner learn the window and also specify a handler to the exception. It could be
Default actions: WinRunner clicks the OK or Cancel button in the pop-up window, or presses Enter on the keyboard. To select a default handler, click the appropriate button in the dialog box.
User-defined handler: If you prefer, specify the name of your own handler. Click User Defined Function Name and type in a name in the User Defined Function Name box.
How does WinRunner recognize objects on the application?
WinRunner identifies the object on the identification properties of the object saved in the GUI Map file. These properties are:
Physical name: like “save” for a save dialog box, or “OK” for an OK button
Logical name: is the name given by WinRunner when adding an object into the repository. In most of the cases WinRunner takes the text which is attached with the object, work as the Logical name.
GUI Map contains the logical name and a physical description in respect to the each object in the application. WinRunner checks that there are no other objects in the GUI map with the same name.