My application uses MS Load test. We are currently running tests configured to Add X threads per minute, up to a given maximum, and once each thread finishes its test, it immediately starts another test.
However, in our production system, we use a queuing system to allow Y users per minute to enter the site. But when each user finishes their purchase, they just log off.
This difference in behavior leads to wildly different results in metrics like orders per minute, even if X = Y, and the maximum number of users on the site is the same.
Is there any way to configure MS Load Test to behave more like the second case? Launch Y number of tests per minute, but when that test finishes, don't run another one?
