seanlon11
17 years agoOccasional Contributor
Load Testing explaination, please
I am trying to sort through what exactly some of the Load Testing parameters mean, and if someone could help, I would appreciate an explanation. I have looked at the documentation, but I still have questions.
I am a novice to load testing, so the more you dumb down the explanations the better
Settings:
There are no assertions in this scenario.
My first question lies in what exactly those 10 threads are doing. Do those 10 threads each send Requests to OrderSubmit and UpdateProfile for 30 seconds? I have multiple theories on what they are doing, but I want to hear from someone else exactly what is happening.
From the example online, I have gathered that the "Test Delay" and "Random" vars are used to separate the time from test to test between 500 and 1000 milli-seconds. However, I do not completely understand what that means. What does the .5 represent (I know it's a var in the random function)? A percentage of the Test Delay? If I put .75 in there, would the tests be separated by 750 and 1000 milli-seconds?
Thanks,
Sean
I am a novice to load testing, so the more you dumb down the explanations the better

Settings:
- Limit = 30 seconds
- Threads = 10
- Strategy = Simple
- Test Delay = 1000
- Random = 0.5
- 2 test steps: OrderSubmit & UpdateProfile
There are no assertions in this scenario.
My first question lies in what exactly those 10 threads are doing. Do those 10 threads each send Requests to OrderSubmit and UpdateProfile for 30 seconds? I have multiple theories on what they are doing, but I want to hear from someone else exactly what is happening.
From the example online, I have gathered that the "Test Delay" and "Random" vars are used to separate the time from test to test between 500 and 1000 milli-seconds. However, I do not completely understand what that means. What does the .5 represent (I know it's a var in the random function)? A percentage of the Test Delay? If I put .75 in there, would the tests be separated by 750 and 1000 milli-seconds?
Thanks,
Sean