LoadRunner Cloud with Azure DevOps Integration
Hi everyone,
I want to talk about LoadRunner Cloud with Azure DevOps integration in this session. If you want to learn more about performance testing, please following my previous article about performance testing and how to manage your Jmeter scripts with LoadRunner Cloud.
Let’s we talk about Azure DevOps plugin : LoadRunner Cloud Extension.
We use the Azure DevOps Server (also known as TFS, Team Foundation Server) and Visual Studio Team Services (VSTS, also known as Azure DevOps) plugin to include a LoadRunner Cloud test as part of a build script.
Firstly, we download the LoadRunner Cloud extension for Azure DevOps.
After then, we install the extension for Azure DevOps. For details, you could review Azure DevOps extension installation help.
After completing these steps, we create a service endpoint. For details, you could review manage service connections help.
When we create the service endpoint, we configure these parameters for LoadRunner Cloud:
- Server URL : URL to connect LoadRunner Cloud server. For example: https://loadrunner-cloud.saas.microfocus.com.
- Authentication : For username/password authentication, enter the following:
User Name. Our user name to log on to LoadRunner Cloud.
Password. Our password to log on to LoadRunner Cloud.
For OAuth authentication, we paste our Client ID in the User Name field, and our Client Secret in the Password field.
- Proxy URL : Add our local proxy in the format http(s)://(host):(port#) or leave empty if you are not using a local proxy.
- Proxy Username : If we use a proxy that requires credentials, we enter the user name.
- Proxy Password : If we use a proxy that requires credentials, we enter the password.
I assume that you already have access to Azure DevOps and have the appropriate access rights to create and run a Pipeline in your organization. If not, it might be the time to create a DevOps ticket for that 😊
In Azure Devops, the steps are as follows:
- LoadRunner Cloud Service Endpoint : We select the service endpoint we created above for our LoadRunner Cloud server.
- Tenant ID : Our tenant ID, specified in our LoadRunner Cloud URL.
- Project ID : Our project ID, specified in our LoadRunner Cloud URL.
- Test ID : The ID for our test. We navigate to Load Tests > Overview > General to see the test ID.
- Send e-mail to the preset address : We select this check box if we want to receive a notification email to a preset address after the test run is finished.
We should attent to this issue that for earlier versions of the Azure DevOps server, we may need to enable the Allow scripts to access the OAuth token option before running the task.
When the task has finished, we can view an artifact published on the Summary tab and a brief report on the LoadRunner Cloud tab.
In this post, we learned that how we will integrate load tests in Azure DevOps using the LoadRunner Cloud. That’s all I’m going to talk about for now. See you in my next post!
Until then,
#HappyTesting ❤️
References:
LoadRunner Cloud Extension — Visual Studio Marketplace
Install extensions — Azure DevOps | Microsoft Learn
Service connections in Azure Pipelines — Azure Pipelines | Microsoft Learn
Cloud Load Testing | Cloud Performance Testing | Micro Focus
