Well I have recorded my test, and set my properties to:
-Simultaneous browsers: 5
But when I run my test on our (scheduling)app it only shows that 1 registration has been made.
There are no user cookies from this app so I am using dynamic user list.
There are 37 SendRequest() calls in the script.
But when I check the test results it says we have only sent 37 requests even though the results form also insists that I have run 5 concurrent browsers.
Why does it lie?!?!?!
Have I forgotten some silly property somewhere?
(I also tried un checking the "Test for existence of Robot.txt" option with no luck)
It's not a "lie", but it seems to be a commonly encountered misinterpretation. The number of iterations is PER browser connection. You have to multiply the number of times you want it to run by the number of users. So 5 connections, 1 time is only one user completing the test. If you want it to run 1 time for all 5, you need to have 5 in the number of iterations. Five times, 25 iterations, etc. Might not seem that intuitive, but that's how it works.
Well that's the silliest thing I've heard today [img]images/icons/blush.gif[/img] )
Well ok now I feel like the office idiot lol I've been trying to figure this out for the past day and a half.
So if I set itereations to equal my simultaneous connections it will actually run the iterations concurrently?
It doesn't appear to run them all concurrently, but then again one processor can only do so much.
Thank you VERY much for the reply Jamie.
Have a great day!
requests that are sent simultaneously doesn't mean that all the requests are hit at the same time in the server end this is not at all provided by ACT. there are other tools in the market space that provide this they stop all the requests at a specific space and then send them at once. for performance testing there are lot of variables that are taken into consideration apart from the basic things.