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
Consider scheduling your load tests for up to 60 minutes. You can always stop the test earlier. By scheduling it for 60 minutes, you retain the option to run the test longer or even pause/resume the test, effectively getting a second test for free. The cost of a shorter test, i.e. 5, 10, or 15 minutes, is the same as a 60 minute test, so there’s really nothing to loose.
We are happy to announce that we recently added support for Firefox 7 to our monitoring and load testing products! You can now explicitly specify the Firefox version your script will run against. Currently we support both Firefox 3.6 and Firefox 7.
For example, the following script will open the Firefox 7 browser and navigate to a url:
var selenium = browserMob.openBrowser("FF7");
browserMob.beginTransaction();
browserMob.beginStep("Home Page");
selenium.open("http://seleniumhq.org/");
browserMob.endStep();
browserMob.endTransaction();
The same is possible when using the Selenium 2.0 API (WebDriver):
Hello Readers!! It gives me immense pleasure in meeting you with yet another article on WebDriver. WebDriver has been creating a lot of buzz among the Selenium community lately and BrowserMob, an active member of the Selenium community, wasted no time in announcing its support for the WebDriver API.
I hope you had the chance to read the great introduction article on the Webdriver API by fellow blogger Ben.
In this article I would like to touch on the basics of scripting with the WebDriver and the BrowserMob API.
I’m sure many of you, who are new to this API are asking yourselves these questions just like I did.
Select any time coordinate in your test plan and simply add a comment in the annotation field. Your annotations are tracked and numbered with a flag, so to review, simply reference the number on the flag in the list of annotations made for that test plan. Don’t worry about making mistakes, you can delete an annotation at any time.
Do you know where your website traffic is coming from? How about the percentage of traffic coming from various regions?
A new report from, comScore, a market research firm, found that nearly 24.1% of total number of users visiting Amazon’s retail website in the month of June, came from the Asia Pacific region. Similarly, 24.9% of the total traffic on Apple’s website are from this same region.
As companies continue to expand their brands globally, it becomes increasingly important to keep track of where traffic is coming from, as load times and performance may vary depending on the region.
Hello Testers – First, I have to admit that I am not a Flex/Flash developer and cannot take credit for the following content. This was produced by my colleague and fellow BrowserMob blogger, Anu. It is documented internally but I believe the BrowserMob community will find value so I scrubbed it and published it.
Overview
Traditionally, testing Flex/Flash applications was difficult because the logic/behavior is encapsulated from the browser. With the introduction of Flex 3.x, came the release of the Adobe Automation Framework; and Gorilla Logic developed a lightweight testing application called FlexMonkey. In conjunction, a Selenium plugin was created – FlexMonkium. Now Flex recording and playback are seamlessly interleaved with native Selenium recording and playback so you can easily automate the testing of hybrid web applications that mix HTML and Javascript with Flex.
Hello Readers!! Welcome back to Part 3 of our Load Testing Best Practices series, which focuses on writing good load testing scripts.
As I’m sure you would agree to, load testing is an imperative part of every development effort. One of the key components to your load testing efforts is a good load testing script that simulates real user behavior on your web site in the most realistic and accurate way possible.
Before you take a deep dive into the scripting, there are few things you need to plan ahead of time.
So you reviewed part 1 of our best practices blog series, “Planning” and now you are wondering about configuring your test. What are all the pieces that need to be thought about and configured? Fortunately these are not complex questions; you just need to know some basic information:
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.
Recent Comments