You’ve run your baseline load tests and you’ve tracked what you think is regular user behavior with browsing, shopping carts, checkout and the like. But as experienced developers, we know one thing: there’s no such thing as “regular user behavior.” So when you’re ready to take your load testing to the next level, try this script showing you exactly how to randomize URLs in your load tests.
We get so focused on the “how” of load testing that we sometimes forget to talk about why load testing is important. Read this if you want to know why it’s important, too. Or, you may already know it is important - but you need to convince a friend, colleague or manager of load testing’s importance. Either way, here are a few useful points to help understand.
Check out this video recording, where we cover the basics of load testing and how to build an automation pipeline using Jenkins executing tests on LoadImpact.com. In the end we'll take a peak view on our next major platform upgrade, built on top of our open source load testing tool - k6
What did you get your application and infrastructure for Load Testing Season?
It's not October yet, but “Load Testing Season” is already upon us. While Load Testing Season isn’t as celebrated as Labor Day, Halloween, Thanksgiving, or Christmas, it’s overriding importance in the world of e-commerce is inarguable.
If you’ve visited the Load Impact app today, you’ve probably already noticed some UI refinements. Based on usage patterns and your input, we’ve streamlined and reorganized features so they’re easier and more intuitive. We’ll describe them below, but you’ll discover them quickly and easily just by taking a few moments to click around the app.
We’re constantly collecting feedback from our users in an effort to improve your favorite performance and load testing software.
Here are a few items we’ve recently pushed live into our app for your convenience.
In the first installment of this mini-series, we outlined how you efficiently prepare for performance testing. In the previous article, we got into the nitty gritty of what tests to run, and how to run them.
The final step toward ensuring you’re shipping high-performance applications and websites is to continuously test throughout your software development lifecycle.
If you’re a DevOps-minded organization that’s already working with Continuous Delivery and Continuous Integration (CD/CI) tools, then you’re off to a great start.
At Load Impact, we build a tool that helps you understand and continuously keep track of your application’s performance at varying levels of traffic.
Our software does this by simulating virtual users interacting with your application. (It's pretty cool, if you ask us and thousands of our users )
Simply put: Load Impact is a performance testing service.
I have worked for Load Impact since its founding, and I’m going to share how we use the tool ourselves.
Tl;dr — More Load Impact customers than ever are continuously running load tests. In response, we’ve just shipped our “Performance Thresholds” feature. Now, engineers set Pass/Fail metrics for their scheduled tests in order to hone in on the data that’s most important to them. Here’s how we think that helps you:
- The binary status of Pass/Fail metrics is great for automated Continuous Integration flows
- Set thresholds for VU load time, page load time or any of your custom metrics
- Know right away if a test passed or failed your expectations
- Configure tests to abort when a metric fails and avoid completely crashing your application