How to Prepare a Scenario to Run
This task describes steps to take before you start running your scenario.
Specify result file name and location
Select Results > Results Settings.
Enter a descriptive name for the result file.
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.
Enter the full path to the folder where the result file will be stored. This depends on the runtime file storage options configured.
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.
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 HPE's Web-based test management program, Application Lifecycle Management, to store results to a project. For information, see Managing Scenarios Using Application Lifecycle Management.
Specify Scenario Runtime Settings
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.Back to top
Set up the monitoring environment - optional
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.Back to top
Enable Automatic Result Collation - optional
You can enable auto-collation before running the scenario if you are using the local machine file storage setting (default setting). If Automatic Result Collation is enabled, LoadRunner automatically collates the results from all the load generators when the screnario run finishes.
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.Back to top
Enable Auto Load Analysis- optional
To invoke 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.
Back to top
Schedule scenario - Optional
Define a schedule for the scenario. See How to Define a Schedule for the Scenario.Back to top
Provide scenario summary information - optional
Select Scenario > Summary Information, and enter the scenario's summary information.Back to top
Set up the scenario to run MMS (Media Player)- optional
Note: This protocol is currently supported for replay only. All support will be removed in a future version.
- 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.
Set up the scenario to run GUI Vusers - optional
If you have integrated a QuickTest or Unified Functional Testing script into the scenario:
Set up runtime settings for the script in QuickTest or Unified Functional Testing. Runtime settings from LoadRunner are not applied to QuickTest or Unified Functional Testing scripts.
- Ensure that QuickTest or Unified Functional Testing is closed before running the scenario.
Note: You can run only one GUI Vuser concurrently per machine.