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.
Remember, too, we narrowed the list for this review to what we consider to be the most popular, open-source load testing tools. This list includes:
- The Grinder
You and your team have been pushing plenty of updates to your app over the last few weeks in preparation for a marketing milestone.
Everybody in the company is excited, and you can’t wait for users — and potential customers — to see what you’ve cooked up for their enjoyment.
But you haven’t been continuously performance testing throughout development (a bad move, but we forgive you), and you just realized it’s time to start running load tests.
Never fear! We’ve broken down a few steps to get your load testing extravaganza up-and-running, and from there you can smoothly transition to continuous testing, which will save you from this headache in the future.
Simulating real traffic patterns is the best way to get actionable results from your load tests. That includes creating tests that closely mirror where your traffic is coming from.
The latest Load Impact update brings the ability to generate load from six additional Amazon Web Services Regions around the world in your load tests.
This webinar not only shows you how to automate load testing in your CI pipeline, but you’ll also learn how Julien applies Microsoft’s best practices to the DevOps and “continuous” mindset while embracing the world of open source software.
Continuous load testing throughout the software development process improves your understanding of your website, application and infrastructure performance.
Developers around the world are discovering that load testing isn’t just a one-off project or something you wait until the last minute to do.
Integrating load testing into your DevOps and Continuous Integration lifecycle helps you achieve a few things.
- Load testing is yet another task you can automate — and we know that’s a good thing
- Understand the performance impact of each code commit
- Plot your app or website’s performance trend over time
The goal of performance testing is to get actionable data that will help you optimize your website, app or API performance.
The best way to do that is to create the most realistic load tests possible. We like to dish out tips on how to do that in many different ways. To name a few:
- Use the Load Impact User Scenario Recorder to create your load testing scripts
- Look at your traffic data in Google Analytics when figuring out how many concurrent virtual users you want to test when figuring out your performance baseline
- Run multiple types of tests to see how your app reacts under different kinds of pressure
The goal for any software developer when performance testing is to get back actionable data from their load tests.
In order to prepare your application and infrastructure for real-world traffic, you need to create user scenarios that mirror real-world behavior.
Instead of asking our users to write custom user scenarios in Lua from scratch, we created the Load Impact User Scenario Recorder. It’s a free extension on the Chrome Web Store.
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.
In the previous article in this series, we talked about getting prepared for your performance testing by:
- Creating user scenarios
- Configuring and running smoke tests
- Creating load tests
At this point, you’re onto the actual testing. You’re running load tests and finding actionable data in the results.
We’ve broken this phase down into six parts, but it’s important to remember that each part may require multiple iterations. But hey, multiple iterations of each step just means you’re continuously finding new features to optimize or new problems to fix, and that will only improve the user experience in the long run.