This task describes steps to take before you start running your scenario.
For details on designing the scenario, see Designing Scenarios.
Select Results > Results Settings.
Enter a descriptive name for the result file.
Enter the full path to the folder where the result file will be stored. This depends on the runtime file storage options configured.
If you are using the default file storage setting (local machine), specify a folder in which to store all of the collated results after the scenario run.
If you specified a shared network drive as the file storage method, specify the folder to which Vuser groups should write during scenario execution.
Select the appropriate options for subsequent scenario runs.
When comparing the results of scenario runs in Analysis, the graph displays all the result sets by name. For example, the image below displays the superimposed results sets of two scenario runs, res12, and res15.
When naming the results files, avoid using the same name when saving to different directories.
You can use HP's Web-based test management program, HP Application Lifecycle Management, to store results to a project. For information, see Managing Scenarios Using Application Lifecycle Management.
This is especially useful for cross results analysis, in which LoadRunner superimposes the results of several scenario runs in a single graph and lets you compare the results of multiple scenario runs. Giving each run a descriptive name enables you to distinguish between the results of the multiple runs displayed later in the analysis graph.
For details on setting global runtime file storage options, see Options > Runtime File Storage Tab. To set runtime file storage options for an individual load generator, see Load Generator Configuration > Runtime File Storage Tab.
You can instruct LoadRunner to allow an individual Vuser or the Vusers in a group to complete the iterations they are running before stopping, to complete the actions they are running before stopping, or to stop running immediately. For details, see Options > Runtime Settings Tab.
LoadRunner enables you to view data generated during the scenario run using the online monitors. Before the run, specify the server machines that the Controller should monitor during the scenario run.
For details, see How to Set Up a Monitoring Environment.
If you are using the default file storage setting—local machine—prior to running the scenario you can enable auto-collation. As soon as the scenario run is complete, LoadRunner automatically collates the results from all the load generators.
Note: Alternatively, you can collate the results manually after the scenario run is complete. For details, see How to Collate Scenario Run Results.
To enable automatic collation, select Results > Auto Collate Results. When this feature is enabled, Auto Collate Results is displayed in the status bar.
If you are working in Expert mode, you can disable the collation of the log files. Select Tools > Options > General tab > Do not collate log files.
To set a post-collation command, select Tools > Options > Execution tab, and enter the command in the Post Collate Command box. For details, see Options > Execution Tab.
To invoke HP LoadRunner Analysis as soon as the scenario is finished running, select Results > Auto Load Analysis. When this is enabled, Auto Load Analysis is displayed in the status bar.
Define a schedule for the scenario. For details, see How to Define a Schedule for the Scenario - Workflow.
Select Scenario > Summary Information, and enter the scenario's summary information.
For details, see How to Define a Schedule for the Scenario - Workflow.
This protocol is only supported for replay.
- When running a scenario in controller for an MMS script the scenario may fail if the runtime setting Network >Speed Simulation is not set to Use maximum bandwidth, and Miscellaneous >Multithreading setting is not "Run Vuser as a process".
- If Media Player scripts fail with the error: Error -86801:Host access denied, <hostname> not available or missing, add the
mms_disable_host_check function to the script.
If you have integrated a QuickTest or Unified Functional Testing script into the scenario:
Ensure that QuickTest or Unified Functional Testing is closed before running the scenario.
In the runtime settings for script dialog box, only the General categories and sub-categories (General, Iterations, Miscellaneous, Think Time) are relevant for QuickTest or Unified Functional Testing tests. The Replay options are not relevant.
Note: You can run only one GUI Vuser concurrently per machine.