Load Testing with Unique EntitiesLast Updated: 12/07/2015 Introduced in Verision: 2.0
The Load Test Utility dynamically generates data and makes requests against the system for load testing purposes. Entities created by a load testing scenario can be uniquely identified by setting their MakeUnique property to true.
To make a created entity unique, select the Script Editor tab in the Load Test Utility, Select the event which creates the entity and, in the XML editor on the right, locate the MakeUnique property and change its value from false to true.
In the example, we will:
- Change a setting in the Load Testing Utility’s Script Editor to create unique entities.
- Set up simulation values on the Testing Control tab and run the scenario.
- View the results in the Log tab and in the portal.
Our example load test will create 10 uniquely-named flows. This example assumes that the script to create a flow has already been created and is called Add Flow.
First locate LoadTestTool.exe in the local machine and open it.
In the Load Test Utility, select the Script Editor tab. In the Scenarios dropdown, select Add Flow. A list of events will appear in the table on the left – each one identified by the service called, the method and the time taken to execute the event. On the right is a scratchpad containing an XML representation of whichever event we select.
We will select the third event in the list, which creates the flow. In the scratchpad, we see an XML representation of the event. Near the bottom, we will locate the name parameter and scroll to the right. We will find that the property MakeUnique is set to false.
We will change the value of MakeUnique to “true”…
…and click the Save button to preserve the change.
Under the Testing Control tab, we will set up our load test. In the Select Script drop-down list, we will select Add Flow. Under Simulation Type, we will select No Pause. In the Number of Simulated Users field, we will enter “10”. Then we will click the Run button to begin the test.
Under the Log tab, we will see that 10 sessions of the Add Flow scenario have started.
Back in the flow, we will find that 10 new flows have been created exactly according to the Add Flow script, with the exception of each flow’s name, which contains an added unique identifier.