Azure Load Testing Series - Create and run a load test

Hey folks!, We have already seen a brief about a high level overview of azure load testing in the first blog of this series. In this blog we will see how to create and run a load test in Azure.


  • In your azure portal select + create a resource and search for Azure Load Testing ( It is still in preview stage when this blog was created )

  • Click on create and provide the required information to configure Azure load testing resource as below

https://dev-to-uploads.s3.amazonaws.com/uploads/articles/xx4bc2i4yjhgae831dhw.png

  • After providing those information , select Review + create , Once it is validated you will be able to select create to start the deployment of the Azure Load testing resource
  • Once you are into the resource , select IAM option and then select add role assignment

https://dev-to-uploads.s3.amazonaws.com/uploads/articles/d0w9wimbgvfq4pa149zj.png

  • Assign either Load Test Contributor or Load Test Owner role to your account.

https://dev-to-uploads.s3.amazonaws.com/uploads/articles/72lcj8qu4jz0iub8ibat.png

  • In the next tab select the members to whom this permission is to be applied and proceed to Review+assign tab

https://dev-to-uploads.s3.amazonaws.com/uploads/articles/ce78frx2s8zqn2w7s0o2.png

  • Once the role is assigned , you will be now able to create a test plan

https://dev-to-uploads.s3.amazonaws.com/uploads/articles/ufg5t7ntu6jru0smn53y.png

  • Provide a Test name and move to next tab Test Plan , In this tab select your JMeter script that we already created as part of previous blog and then select Upload to upload the file to azure.

https://dev-to-uploads.s3.amazonaws.com/uploads/articles/e16l4d9b8riv139mtne0.png

  • We can skip to last option and click on create, as we will be covering in detail about monitoring and parameters in a separate blog :)
  • As soon as we created the test plan it will start to run by default ( we can modify it while we creating the test plan if we don’t need to run it after the test plan creation)

https://dev-to-uploads.s3.amazonaws.com/uploads/articles/qeb4gxavcz8rmsbuhu4u.png

You can see the clien-side metrics while the test is running. By default the data refreshes every five seconds

  • Let’s modify our JMeter script to have 100 concurrent users and see how our application performs for high scale loads

https://dev-to-uploads.s3.amazonaws.com/uploads/articles/qeb4gxavcz8rmsbuhu4u.png

  • We could see there is a increase in response time and performance of our application.
  • We also have an option to compare between test plans , to do so I reran our previous tests for multiple times and in the Test blade you need to select test plans that you want to compare and click on compare

https://dev-to-uploads.s3.amazonaws.com/uploads/articles/wfnavnq6bos6wk4hy8hn.png

https://dev-to-uploads.s3.amazonaws.com/uploads/articles/rtnj2npocqcqd4ju7aim.png


In our next blog we will see how to create Continuous regression testing (CI/CD) using Azure pipelines


Please go ahead and join our discord channel (https://discord.gg/8Cs82yNS) to give some valuable feedbacks