Share this page

# LoadRunner Cloud

Use the LoadRunner Cloud bundled plugin to run OpenText Core Performance Engineering performance tests and deliver the test report to PulseUno.

To configure the step:

1. Add the 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.
   URL | Enter the URL of your OpenText Core Performance Engineering instance, for example: https://loadrunner-cloud.saas.microfocus.com
   Username | Enter the username of the administrator account to connect to the OpenText Core Performance Engineering instance.
   Password | Enter the password of the administrator account to connect to OpenText Core Performance Engineering.
   Tenant ID | Enter your OpenText Core Performance Engineering tenant ID. You can copy the tenant ID from your OpenText Core Performance Engineering URL, for example: https://loadrunner-cloud.saas.microfocus.com/home/?TENANTID=123456789&projectId=1
   Use OAuth token | To use OAuth instead of the username and password, select Use OAuth token and specify the Client ID and Client Secret.
   Project ID | Enter your OpenText Core Performance Engineering project ID. You can copy the project ID from your OpenText Core Performance Engineering URL, for example: https://loadrunner-cloud.saas.microfocus.com/home/?TENANTID=123456789&projectId=1
   Load test ID | Enter the ID of the test. To find the test ID, in OpenText Core Performance Engineering, select Load Tests and highlight the test. The test ID is displayed in general information in the right pane.
   Create report file | (Optional) Select this option to generate a PDF file containing the OpenText Core Performance Engineering test results and attach it to the chain. After the chain runs, you can review and download the report file on the chain run page. For details, see View chain runs.
   Use advanced options | (Optional) Select this option and specify additional test run details: Load test run ID. To pick up the results of a previous test run, enter the run ID. Use this option when you are re-running the chain and don't want to trigger a new test run in OpenText Core Performance Engineering. Check status every (in minutes). Specify how often to poll for test run status, in minutes. Default: every minute. Check timeout (in minutes). Specify how long to wait for the test run to complete before timing out, in minutes. The minimum timeout is 5 minutes. Default: 60 minutes.
   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. Deactivated 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.

The plugin step triggers a load test in OpenText Core Performance Engineering and displays the test results on the chain run page in PulseUno.

Back to top

See also:

- Create chains
- LoadRunner

https://admhelp.microfocus.com PulseUno 8942
Tips to improve your search results... PulseUno Help Center PulseUno Help 24.2 - 25.2 All View Local Help Center View Online Help Center Version: