Load Testing Blog
Showing posts tagged “stress testing”
Introducing the OkHttp extension for MuseIDE
The Muse Test Framework is designed around extensibility – and specifically around the ease of adding new types of steps and value sources. The intent was to make it easy for 3rd parties to add new abilities to the framework and have those abilities seamlessly integrated into the MuseIDE without much effort. This made it a natural choice for us when looking to develop new load testing capabilities beyond our current tools such as Load Tester.
This first version of the OkHttp extension is very simple – almost embarassingly so. It provides just a handful of new … Continue reading »
Mail Server Load Testing
Mail servers can be load tested by sending a large number of emails to a mail server over a specific period of time and recording how the server behaves as it receives those connections. Organizations may require this type of load testing for several reasons. For example, they generally receive a consistent, low level of mail traffic with intermittent periods of high traffic. They may also expect growth within a certain period of time and want a mail server that is capable of scaling with the organization’s growth.
How To Manually Modify HTTP Requests in Load Tester 4.2
In older versions, Load Tester provided a simple interface for modifying the URI portion of an HTTP request. For example, you could add a query parameter or a path segment by adding it directly to the request line in the Edit HTTP Request-line/URL dialog.
In Load Tester 4.2, this process has been made slightly more complex but vastly more powerful. We’ll start by manipulating the URI field directly. To do so, select the specific transaction you wish to edit, then select the Fields View, then choose “Customize” from the “Choose customization” drop-down menu in the upper right … Continue reading »
Knowing your Security with Stress Testing
In the past, we’ve had plenty of discussion on how performance effects user experience, and how that relates to conversions. But, can a server’s performance effect it’s security?
During a previous test, we had a customer whose site included a contact form. The user would complete the contact form in their browser, and the application server would convert this response into an e-mail and send it through a mail server. The contact form, coupled with the use of a CAPTCHA, helps to cut back on undesirable messages. During our testing, we discovered that the mail server was becoming overloaded (at only … Continue reading »
Case study: Lenox Finds a Baseline in the Cloud
For Lenox, makers of fine china and crystal, e-commerce has been an important aspect of the business for over ten years. When Lynch needed to test the Lenox website user capacity on short notice, Load Tester was the right tool for the job. It offered the features and flexibility to build complex, realistic test cases and identify performance bottlenecks. Read more about their experience.
Load Testing Fallacies: The Test Scenarios Must Be Completely Accurate
Last time, I talked about why it is ok to start testing early in the development process. I’m going to continue that thought process to discuss load testing without complete performance requirements. This Load Testing 101 article says “If the real end user is going to do work with your application in a totally different way than you test you are as good as with no testing at all.” While there is a nugget of truth hidden in there, it is easy to take away the wrong understanding.
One interpretation of that statement would be that “you must have … Continue reading »
How User Ramping Works – Part One
How we add new virtual users to a test can be confusing when you’re first starting out with Load Tester, and sometimes can result in tests that do not ramp up to the number of users you expect or otherwise behave strangely.