How to Configure Winrunner Settings (1)
Introduction To WinRunner Basics
(Continued from previous question...)
How to Configure Winrunner Settings (1)
Properties for a Single Test
The Test Properties dialog box enables user to set properties for a single test. User set test properties to store information about a WinRunner test and to control how WinRunner runs that test.
To set test properties:
Choose File > Test Properties.
The Test Properties dialog box opens. It is divided by subject into six tabbed pages.
They are General Enables user to set general information about the test.
Description Enables user to enter descriptive information about the test.
Parameters Enables user to define input and output test parameters.
Add-ins Enables user to indicate the add-ins required for the test.
Current Test Enables user to review the current folder and run mode settings for the test.
Run Enables user to define startup applications and functions.
User can enter the name of the test author and choose whether the test is a main test or a compiled module. User can also specify a Microsoft Excel file to use for the test’s input data. User can view other summary information’s like Name of the Test, Location within the File System, Date and Time that the test was created and the Read/write Status.
User can enter a Description Summary of the test, the application feature(s) user is testing, a reference to the relevant functional specifications document(s), and additional details about the purpose, contents, or requirements of the test.
User can manage test parameters by adding (declaring), modifying, and deleting parameters in the Parameters tab. The Test Parameters list displays the existing test parameters. When the test is called by another test, the input parameters that are listed in the Parameters tab are assigned the values supplied by the calling test, and the output parameters return values, generated within the current test, to the calling test. Because parameter values are assigned sequentially, the order in which parameters are listed in the Parameters tab determines the value that is assigned to a parameter by the calling test. In test calls, input parameters always come before output parameters. Test parameters are used only in tests of type Main Test. They are not used in compiled modules.
Add-Ins is used in WinRunner to load functions specific to the particular add-in to the memory. While creating a script only those functions in the add-in selected will be listed in the function generator and while executing the script only those functions in the loaded add-in will be executed else WinRunner will give an error message saying it does not recognize the function User can indicate the WinRunner add-ins that are required for a test by selecting them in the Add-ins tab. User can see which add-ins are loaded at any time in the About WinRunner dialog box (Help > About). Loaded add-ins are marked with a “+”.
User has a read-only view for this Tab. The different options available are:
Current line number this box displays the line number corresponding to the current location of the execution arrow in the test script.
Current folder this box displays the current working folder for the test.
Expected results folder
This box displays the full path of the expected results folder associated with the current test run.
Verification results folder
This box displays the full path of the verification results folder associated with the current test run.
This box displays the current run mode: Verify, Debug, or Update.
User can also use the getvar function to retrieve the value of all the options available in the Current Test tab.
User can define startup application and startup functions. User can also select whether or not to run the startup application and/or function before running the test.
Defining a Startup Application
When defining a startup application, user can specify the path to the application, any required parameters, and the amount of time WinRunner waits between invoking the application and running the test. User can also select how the application window to open.
Defining a Startup Function
A startup function can be either a TSL function or a user-defined function contained in a compiled module. When defining a startup function, User specify the name of the function, function parameters (if any), and the compiled module name and type (for user-defined functions).The function name can contain only alphanumeric characters and underscores. It cannot begin with a number or contain parentheses. If the function is part of a compiled module, user has to select the compiled module type in the Load module as a box.
Global Testing Options
User can control how WinRunner records and runs tests by setting global testing options from the General Options dialog box. The values set by the user remain in effect for all tests in the current testing session. When the user end a testing session, WinRunner prompts to save the testing option changes made by the user to the WinRunner configuration. The General options dialog box contains the following categories
General Contains options for GUI map preferences, language settings and other general testing options.
Folders Specifies the folder location of WinRunner files and the search paths for resolving relative paths.
Record Contains the options for recording tests.
Run Contains options for running the test.
Notifications Enables user to specify the criteria for sending e-mail notifications.
Appearance Contains options for controlling the appearance of WinRunner.
The different options available are:
Back up test script automatically every __ minutes
This option Instructs WinRunner to create a backup file in the test folder called script.sav for the script periodically, according to the specified interval.
(Continued on next question...)
Other Interview Questions