Some of the more popular tools out there include LoadRunner and Fiddler. Both of these have a bit of a learning curve. When you want to run a stress test, you just want to run a stress test – not figure out how to configure a complex tool. That’s the main reason I still resort to Microsoft’s (ancient) Web Stress Tool. This lightweight tool does a lot of what LoadRunner does – except, unlike Loadrunner, it only takes a few seconds to configure a load test.

Creating a new test script

screenshot_stress_tester_create_new_script

1. Create new script – Manual option.
2. In the ‘Server’ type – www.myserver.com

3. In the script items (lower half of the right screen) – type the actual URLs of the pages (ASPX, asp, php, jsp whatever…). E.g.
    /index.aspx – in the Path. Configure additional items (if you want your load test to round robin over a set of pages, just enter them all one at a time as shown in the figure above).

Setting the Load

screenshot_stress_tester_number_of_connections

  1. Expand the ‘New Script’ node on the Left Hand Side – ‘Settings’ –> Stress level (threads) – set to whatever the load is (100, 200….)
  2. Setting the test run time – The above load can be distributed over a period of time – set this in the ‘Test Run Time’ (same place as the Stress Level setting above).
  3. Run the script using the ‘run’ option in the top menu.

Summary

Whenever I need to run a quick Load Test, Microsoft’s Stress Test tool does the job well. I wish they hadn’t discontinued it (there doesn’t even seem to be a 64 bit version around).

Anuj holds professional certifications in Google Cloud, AWS as well as certifications in Docker and App Performance Tools such as New Relic. He specializes in Cloud Security, Data Encryption and Container Technologies.

Initial Consultation

Anuj Varma – who has written posts on Anuj Varma, Hands-On Technology Architect, Clean Air Activist.