Have you integrated your automated scripts from TestDirector?
When we work with WinRunner, we can choose to save our tests directly to our TestDirector database or while creating a test case in the TestDirector we can specify whether the script in automated or manual. And if it is automated script then TestDirector will build a skeleton for the script that can be later modified into one which could be used to test the AUT.
What are the different modes of recording? - There are two type of recording in WinRunner.
> Context Sensitive recording records the operations we perform on our application by identifying Graphical User Interface (GUI) objects. Analog recording records keyboard input, mouse clicks, and the precise x- and y-coordinates traveled by the mouse pointer across the screen.Reply
Have you performed debugging of the scripts?
Yes, We 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.Reply
How does WinRunner evaluate 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, We can view the expected results and the actual results from the Test Results window.Reply
Have you created test scripts and what is contained in the test scripts?
How you used WinRunner in your project?
Yes, I have been using WinRunner for creating automated scripts for GUI, functional and regression testing of the AUT .Reply
Write and explain compile module?
Write TSL functions for the following interactive modes :
> Creating a dialog box with any message we specify, and an edit field.
> Create dialog box with list of items and message.
> Create dialog box with edit field, check box, and execute button, and a cancel button.
> Creating a browse dialog box from which user selects a file.
> Create a dialog box with two edit fields, one for login and another for password input. Reply
Why you use reload function?
If we make changes in a module, We should reload it. The reload function removes a loaded module from memory and reloads it combining the functions of unload and load .
> The syntax of the reload function is :
reload ( 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 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)
How do you load and unload a compile module?
In ordr to access the functions in a compiled module we ro load the module, We can load it from with in any test script using the load command ; all tests will then be able to access the function until we quit WinRunner or unload the compiled module.
We 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 we 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)
> The unload function removes a loaded module or selected functions from memory.
> It has the following syntax :
unload ( [ module_name | test_name [ , "function_name" ] ] ); Reply
How do you declare arrays?
The Following syntax is used to define the class and the initial expression of an array. Array size need not be defined in TSL.
class array_name [ ] [=init_expression]
The array class may be any of the classes used for variable declarations (auto, static, public, extern). Reply
How do you declare constants?
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 we exit WinRunner.
The syntax of this declaration is :
[class] const name [= expression]; Reply