Stress Testing Scheduling

[Nate]

Hello,
          I was wondering, is there a way to do stress testing on the web server to simulate multiple users? Or setup the scheduling server to run multiple tests concurrently?

[Daniel Levy]

Hi Nate,

At this time, WebUI Tests cannot be converted to web tests / load tests. Our team is reviewing such functionality for a possible enhancement to a future release.

Take a look at what's coming in the next release of WebUI by visiting our Testing Tools product roadmap.

All the best,
Daniel Levy
the Telerik team

[Nate]

I've created a simple application to do this. Please see the attachment. It requires the .Net 3.5 framework to be installed on your machine and WebUI. It can be run via both the command-line and via the Windows Form interface. To run it via the command line type in:

QA.TestFileLauncher "<Path to Test Runner>\ArtOfTest.Runner.exe" "<Path to Test File>\<test.aii>" <#> "<Output file path>"

Note: Each value enclosed in <> is a variable that you should replace with the appropriate value. The <#> represents the number of times the test file or test list file should be executed.


You can schedule the running of this tool using Windows Task Scheduler. The use of the Windows Task Scheduler is not covered here but you can Google (http://www.google.com/search?q=Windows+Task+Scheduler) it for more information.

[Jason]

Nice work Nate - thank you!

Not to minimize your work at all, but I've employed a somewhat less elegant solution whenever I've wanted to run multiple iterations of the same test in a loop in a stress/load testing situation.  It essentially involves creating an infinite-loop batch file that runs the .aii test from the command line:

:TOP
ArtOfTest.Runner.exe [aii or list]=[path to desired test or test list]
ping 1.0.0.0 -n 1 -w 5000 >NUL
Goto TOP

This batch script would run the test or test list over and over again with a 5 second delay in between each iteration.  The Windows task scheduler can be employed here as well, to run the script for a set amount of time.

[Nate]

Jason,
          Thanks for your input. Just a question, why are you pinging the address 1.0.0.0 in your bat file?

[Jason]

It's just an arbitrary way to create a 5 second delay.  The fact that the IP address 1.0.0.0 isn't a real IP doesn't matter very much in this case, because regardless of the fact that the ping won't be successful, it's only going to try to ping it for 5000 milliseconds, which is all that needs to be accomplished. 

1.0.0.0 could be substituted for any IP address you can think of, but the catch is that it has to be one that you can't actually ping - otherwise the command will complete in much less time than 5000 milliseconds.

[Nate]

Jason,
          Ok that makes sense, but I would like to mention that the 1.0.0.0 IP is in public range and therefore it could be reached. See here for more details- http://bgpmon.net/blog/?p=275. I would suggest changing your script to an IP in one of the private network ranges that you're not currently using at the office. The private network ranges are 10.0.0.0 – 10.255.255.255, 172.16.0.0 – 172.31.255.255, and 192.168.0.0 – 192.168.255.255. This will ensure that you won't hit the IP (aside from any network topology changes at the office).

[Jason]

Wow - solid point.  Thank you!  I have to admit it was pretty ad hoc on my part - I've left that IP in the script simply because it's been working so far.  But I'll definitely update the specific IP I'm using to avoid future issues.