Run performance tests

This section describes the workflow for running a performance test, and the available options for managing the test run.

Performance test run flow

After planning, designing and scheduling your performance test, you run it to create load on your application and to test its performance.

The following table explains the various stages of the test run flow.

Run stage

Description

Start of run

At the start of the run, the Controller checks the test configuration information, invokes the applications that were selected to run with the test, and then distributes each Vuser script to its designated load generator. When the Vusers are ready, they start running their scripts.

During run

During a test run, you can use online monitors to view performance test runs. LoadRunner Enterprise displays information about the load that Vusers generate on your web server and other applications in real-time during test execution. You can also drill down to see which Vuser actions are causing the application problems.

The online graphs display performance data collected by the monitors. You use this information to isolate potential problem areas in your system.

Service Virtualization: During the run, specified virtualized services run instead of the actual services. You can update services during the test run.

End of run

The test run ends when all the Vusers have completed their scripts, when the duration runs out, or when you terminate it.

At the conclusion of the performance test, you can view a summary and graphs of the data collected from these monitors during the test run. For details, see View test data and results.

Back to top

Manage a performance test run

This task describes the workflow for running a performance test, and the available options for managing the test run.

  1. Prerequisite

    Make sure that the performance test you want to run is valid. For details, see Design a test.

  2. Begin test execution

    1. From the LoadRunner Enterprise navigation toolbar, click and select Test Management (under Testing). Create a test set that includes an instance of the performance test you want to run. For user interface details, see the Create, edit, or assign a test set.

    2. In the Performance Test Set pane, select a performance test and click Run Test. The Run Test dialog box opens, enabling you to reserve a timeslot for the test run. For details, see Run Test.

    3. Select an available timeslot and click Run.

      The Initializing Run page opens, and displays the performance test initialization steps performed by LoadRunner Enterprise, and the status for each step. For details, see Initialization steps.

      If each step is completed successfully, the performance test starts running and the Performance Test Run page opens.

  3. Manage Vusers during the test run - optional

    You can override the defined schedules and manually control the behavior of Vusers during a performance test run.

    For task details, see Manage Vusers during a test run.

  4. Manage virtualized services during the test run - optional

    You can stop, start, update, and load virtualized services during your performance test run.

    For task details, see Manage virtualized services during a test run.

  5. Manage monitors, monitor over firewall machines, and load generators during the test run

    You can perform actions related to the status and management of runtime monitors, monitor over firewall machines, and load generators during a performance test run.

    For task details, see Manage monitors and load generators during a test run.

  6. Modify timeslot duration during the test run

    You can extend or shorten the duration of the current timeslot during a performance test run. For details, see Change timeslot duration.

  7. Manually stop the test run and collate run results - optional

    You can manually stop a test run, for example, if you want to delay data collection and analysis until a more convenient time.

    Action Description
    Stop the test run gradually

    On the Performance Test Run page, click Stop Run. The Stop Run dialog box opens, which prompts you to select a post-run collation option (unless a post-run action was set by the system administrator for the project). Select an option, and then click Stop. All Vusers in the test move to the Gradual Exiting state.

    • Collate and analyze results. LoadRunner Enterprise collates the run data from the load generators and generates analysis data. After data is collated, LoadRunner Enterprise automatically deletes the temporary results from the load generators and controllers. You can display the results using analysis tools such as graphs and reports, or download the results for analysis on a local machine. This option takes the most time.

    • Collate results. LoadRunner Enterprise collates the run data from the load generators. After data is collated, LoadRunner Enterprise automatically deletes the temporary results from the load generators. You can download the raw results from the Results tab, or manually analyze results at a later point from the Results tab. This is the default setting.

    • Do not collate results. Frees the machines immediately after the test ends. You can collate and analyze results at a later point from the Results tab.

      Note: This option is not available when the collate at runtime option is selected in Test Options. For details, see Configure general test options.

    • Free current timeslot. Frees the current timeslot once the test has stopped.

      Note: When this option is not selected, timeslots with less than 27 minutes remaining are automatically released.

    Stop the test run immediately

    After clicking the Stop button in the Stop Run dialog box, the Stop Run button on the Performance Test Run page changes to Stop Now . Click the button to stop all Vusers immediately.

  8. View test results and manage result files

    You view and manage result files generated by the test run in the Test Runs view. For user interface details, see Manage test runs and results.

    You can also view performance measurements and results offline in the Offline Results page. For details, see View test results offline.

  9. Analyze test run results

    You use LoadRunner Analysis to analyze test run data offline, from any computer on which Analysis is installed. For information on how to access your project from Analysis, see the Use LoadRunner Analysis to analyze performance test results.

    If there are SLAs defined for the performance test, you can calculate SLA results, and view these results in the Analysis Summary report and SLA report which can be accessed from the Test Run's Result tab. For details, see Manage test results.

  10. View performance improvements and regressions

    You can use the Trend Reports feature to view improvements or regressions in performance across several test runs. For details, see Create trend reports.

  11. Generate reports

    You can generate reports to monitor and manage the usage of LoadRunner Enterprise resources. For details, see Reports.

Back to top

Initialization steps

When you start a performance test, the Initializing Run page opens, displaying the performance test initialization steps performed by LoadRunner Enterprise and the status for each step.

UI Elements

Description

Test Name The name of the test.
<Run Date and Time> The date and time of the test run.
By The user responsible for running the test.
Timeslot Name The name of the test run timeslot.
Duration The time that the test takes to run.
Vusers The number of Vusers reserved for the timeslot.
Machines The number of hosts requested for this test.
<Progress Chart> Displays test initialization steps progress in percentage.
Step Name

The Initialization steps are described below:

  • Register Run. LoadRunner Enterprise initializes the run process.

  • Validate Scripts. LoadRunner Enterprise checks that the selected scripts' Run Logic runtime settings are in sync with the scripts' state.

  • Get Reservation Data. LoadRunner Enterprise checks the required resource information from the selected timeslot.

  • Provision Docker/Cloud LGs. LoadRunner Enterprise provisions the required number of Elastic Docker and/or Elastic Cloud load generators and connects them to the Controller. This step shows how many load generators are ready out of the total number requested.

  • Check Disk Space. LoadRunner Enterprise checks that there is enough disk space on the Controller.

  • Launch Controller. LoadRunner Enterprise initializes the Controller so that other testing entities, such as load generators and scripts can connect to it. If there is a problem launching the Controller, LoadRunner Enterprise automatically attempts to find an alternative Controller. This attempt appears as an additional initialization step. If no alternative Controller is available, the step fails.

  • Download Scripts. LoadRunner Enterprise downloads the required Vuser scripts.

  • Connect To Load Generators. LoadRunner Enterprise checks that the required load generators are valid and connects them to the Controller. If this step fails, LoadRunner Enterprise attempts to find alternative load generators automatically. If this step still fails, check the test definitions and select different load generators for the test.

  • Start Controller Services. LoadRunner Enterprise initializes the Controller's configuration settings in preparation to run the performance test.

Description

A detailed description of the current status of the step.

Status

Displays whether the step passed or failed.

System Messages

Displays error messages generated when a step fails. These error messages can also be viewed from the Event Log. For details, see View test run event logs.

Back to top

Troubleshoot start run failure

Problem Description: Starting a load test fails with a timeout error in the Launch Controller step.

This can be caused by the LoadRunner Enterprise system user not having COM access permissions to start a load test, even if the user is in the Administrators group (where the Administrators group lacks the default COM access permissions for the COM machine wide security configuration).

Troubleshooting: Add the LoadRunner Enterprise system user to the local Distributed COM Users group. All members of this group have local launch and access permissions for COM objects being used by the product.

Back to top

See also: