Our Professional Services team has been extremely busy over the past several months helping Customers prepare for what proved to be a very busy online shopping season. I’d like to share with you a couple of unique challenges that we came across and how we were able to use the BrowserMob platform and some special customizations in order to successfully test what normally would be impossible using just Selenium or a traditional http-based testing approach.
File Uploads
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.
This is the first part of a five-part blog series that will cover all the aspects of load testing, including planning, configuring, scripting, executing and analyzing. This first article focuses on the key areas and questions to consider when planning to run a test.
I generally see customers greatly OVER-estimating their expected capacity and many are often shocked when they get the first set of test results back from us. Usually, there is a lot of work to do in order to get the website or application tuned up and ready for a full production release.
For many years, Customers have come to us and have asked to load test everything from Active X controls, Java applets, Flash, you name it. Until recently though, this was always a monumental and sometimes impossible task to undertake with emulated browsers.
The BrowserMob local validator is a great tool that helps you quickly and easily debug Selenium-based BrowserMob scripts right on your desktop. This article focuses on a couple quick tips to help you get Eclipse optimally configured for use with local validator.
Once you’ve downloaded the local validator and launched Eclipse, you can create an External Tools configuration to help you quickly launch your scripts with the click of a single button. From the Run menu, select External Tools and click on “New Configuration”:
Name the configuration and fill in the path to the local validator .bat file under “Location”:
This article covers how BrowserMob can be used to test mobile websites by modifying the User-agent header and connection speed to match the desired device (iPhone, Android, etc.).
When deciding which version of the website to serve up, most mobile-enabled web applications rely on parsing the User-Agent http header. By modifying this value, BrowserMob Real Browser Users (RBUs) can be turned into “Mobile Browser Users”.
The first step is to determine what specific devices you want to simulate. Zytrax has put together a great compilation of the various different mobile browser user-agent strings here.
Once you’ve determined the User-Agent strings you want to test, the next step is to update the script to overwrite the standard User-Agent header in Firefox. This can be done via the following snippet:
Recent Comments