Skip to content

Home

Jump to bottom
Daniel Danan edited this page Dec 10, 2019 · 18 revisions

Welcome to the LoadRunner Enterprise plugin for Azure DevOps / Microsoft Team Foundation Server

Run a LoadRunner Enterprise Test task from Azure DevOps / Microsoft Team Foundation Server CI build process

  1. Go to the build definition of your Azure DevOps / TFS collection and add the LoadRunner Enterprise Test task. Adding Task
  2. Provide the required input for the LoadRunner Enterprise Test task. To avoid conflicts with the way Azure DevOps / TFS manages secret input, this task performs minimal validations to ensure the input is correct.
  • Display Name: Enter a name to distinguish this build step from other steps.
  • PC server and port: Enter the hostname or IP address and port of a LoadRunner Enterprise server in the format: http(s)://(PCServer):(port). The default value being: http://mypcserver:80.
  • User name: Enter the user name required to connect to the LoadRunner Enterprise server.
  • Password: Enter the password required to connect to the LoadRunner Enterprise server. Note: You can create a variable of type secret in the Azure DevOps / TFS build to store the password, and specify the variable to avoid exposing a password in the build configuration. For example, '$(PCPassword)').
  • Domain: Enter the LoadRunner Enterprise domain in which the test to run is stored.
  • Project: Enter the name of the LoadRunner Enterprise project in which the test to run is stored.
  • Test ID: Enter the Test ID. You can get the ID from “LoadRunner Enterprise” > “Test Management” > “Test Plan view”. Select your test and find the ID in the General Details: Test Name (Id).
  • Test Instance: Select an option for adding the Test Instance ID:
    • Automatically select existing or create new if none exists. If you select this option, LoadRunner Enterprise creates a test instance or locates the existing test instance.
    • Manual selection. Enter the Test Instance ID (available from “LoadRunner Enterprise” > “Test Management” > “Test Lab” > Performance Test Set view).
  • Proxy URL: Add your local proxy in the format http(s)://(host):(port#), or leave empty if not using a local proxy.
  • Proxy user name: If you use a proxy, enter the user name.
  • Proxy password: If you use a proxy that requires authentication, enter the password. Note: You can create a variable of type secret in the Azure DevOps / TFS build to store the password, and specify the variable to avoid exposing a password in the build configuration. For example, '$(ProxyPassword)').
  • Post Run Action: Choose an action to perform when the run is finished: Collate Results, Collate and Analyze (default and recommended value), or Do Not Collate.
  • Trending: (Available only when Collate and Analyze is selected as the Post Run Action) Select a trend report option:
    • Do Not Trend: No trend report is created (default value).
    • Use trend report associated with the test: If Auto Trending is selected in the Load Test, select this option to automatically publish trend results (recommended if you have associated the Performance Test with an associated trend report).
    • Add run to trend report with ID: If you select this option, enter the trend report ID.
  • Timeslot Duration: Enter a duration for the Ad-Hoc timeslot. The minimum time is 30 minutes. Maximum: 480 hours
  • Use VUDs: Choose whether to use a Virtual User Day (VUD) license. This provides you with a specified number of Vusers (VUDs) that you can run an unlimited number of times within a 24 hour period. Before using this option, make sure that VUDs licenses are applied in your LoadRunner Enterprise environment.
  • Status according to SLA: Select this option to set the build-step status according to a predefined SLA (Service Level Agreement) configured within your performance test. If you do not select this option, the build-step will be labeled as "Passed" as long as no failures occurred.
  • On Timeslot creation failure: Introduced in version 1.0.1. If the timeslot cannot be created:
    • Do not repeat: the task ends.
    • Repeat with the following parameters: the task will try several times (according to the value set in the 'Number of attempts'parameter below) to recreate the timeslot to run the test. The task will wait a fixed delay (according to the value set to the 'Delay between attempts' parameter below) between each failing attempt and the next attempt.
      • Delay between attempts: Time (in minutes) to wait between a failed attempt and the next attempt (the minimum is 1 and the maximum is 10).
      • Number of attempts: How many attempts to run the test (the minimum is 2 and the maximum is 10).
  • Artifacts directory: Enter the path to the artifacts directory where the result files are stored.

Task configuration 3. Run the Build. Build running 4. Review the reports from the artifact. Task report in build artifact

Clone this wiki locally