LoadRunner

Use the LoadRunner bundled plugin to run LoadRunner Professional performance tests.

For details about LoadRunner test scenarios, see the LoadRunner Professional help.

To configure the LoadRunner step:

  1. Add the LoadRunner step to a chain, as described in Create chains.

  2. Enter the plugin configuration details:

    Field Description
    Title Enter a name for the plugin step or accept the default name.
    Tests

    Specify the list of test scenarios to run. Enter the relative path to each test file on a separate line, for example:

    scenario\Scenario1.lrs
    scenario\Scenario2.lrs

    Results directory

    Enter the relative path to the directory that will contain the test results.

    Leave empty if the test results are in your workspace directory.
    Time out

    (Optional) Set a timeout after which the step fails, in seconds. Default: 600 seconds.

    Leave empty to run the step indefinitely.
    Advanced settings

    (Optional) Select Advanced settings and specify the following options:

    • Controller polling interval. Specify how often to poll the Controller for the scenario status, in seconds. Default: 30 seconds.

    • Scenario execution timeout. Specify how much time to allocate for running all the scenarios, in minutes. Default: 10 minutes.

    • Errors to ignore. Specify the errors to ignore during the run. Enter each error string on a new line.

    • Analysis template. To apply a template for the build, specify the path to a .tem file. Leave empty to apply the default template.

    • Display controller. Select this option to display Controller during the run.

    • Summary data log. Specify the log options, such as the polling interval for displaying messages and what information to display.
    Attach test reports Select this option to make test report files available in the chain run's Logs tab.
    Control options

    (Optional) Define the control options for the plugin step:

    • Enable step. By default, the step is enabled to run. Clear this option if you need to deactivate the step.

      Disabled steps are skipped when the chain runs.

    • Fail the step. Specify the conditions for failing the step, such as unit test failures, findings criteria, and/or console log entries.

    • Mark step as unstable. Specify the conditions for making the step unstable, such as unit test failures, findings criteria, and/or console log entries.
    Output variables (Optional) Specify the output variables to be passed to other steps down the chain. For details, see Publish output variables.

Back to top

See also: