Stay in the driver’s seat and in control!  When launching a new website or application there are many things to consider to get ready to go “live” – and one of the most important aspects is load testing.

Simply put, load testing helps you determine how many customers the website or application will support – before you potentially find out the hard way (i.e. when users actually come to your site and you have to scramble to make last minute capacity improvements).

Following our blog series on Load Testing Best Practices, Webmetrics will be hosting a Twitter Chat for you to ask any and all questions about load testing.

We just wrapped up our five-part Load Testing Best Practices series. We hope you find these steps simple and convenient as you embark on your next load test.

Planning
When planning a load test, make certain you take all variables into account. For instance, before you load test a website or application, you should ask yourself the following: How much load should I test with (stress test vs. load test)? How many tests should I run? Should I test on a real or virtual browser? Once you have answered these, you will be ready to start and configure your test.

The BrowserMob API has two methods that come in handy when you want to pause a test that has exceptionally lengthy scripts running, such as loops that repeat certain actions several times over the course of the script execution.

By default, when a test is paused, BrowserMob will wait for the actively running scripts to finish executing and complete the current transaction. Long running scripts with loops or scripts testing a streaming video will not be interrupted until they complete. So in order to abort such transactions immediately on pausing, it is important to include the method browserMob.quickStop() at the top of the script as in the example below:

We are happy to announce BrowserMob Proxy a new open source tool for simulating network conditions.

Some early functionality:

  • It can slow down network traffic, effectively simulating what a low-bandwidth user might experience.
  • It can also easily intercept certain HTTP requests (via regular expression), allowing you to mock out unexpected results, such as 500 response codes, long delays is responses, or even unexpected content.

Please visit the main page to sign up for the mailing list, we’d love to get more people involved in the project.You can also go to the  Git project page, where you can check out the source code and report bugs.

© 2012 The BrowserMob Blog Suffusion theme by Sayontan Sinha