Load Testing on a Strict Deadline

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.

Read More

More Load Zones for More Realistic Load Tests

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.

Read More

Better Testing with Visual Studio for Developers and DevOps: Webinar Recap

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.

Read More

Webinar: Better Testing with Visual Studio for Developers and DevOps

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
Read More

What Does the Geographic Location of Your Users Have to do With Load Testing?

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
Read More

Bigger Tests, Same Low Prices

This is the time of year when you’ll often hear people say, “New year, new me.”

While plenty of resolutions will be broken by the end of January, we’ve made a change that we simply can’t go back on now.

We’re very excited to announce that we’ve increased the number of concurrent virtual users our premium subscribers can configure in their load tests — at no extra charge!

Read More

Creating Realistic Load Tests with the Load Impact User Scenario Recorder

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.

Read More

Load Testing Execution Phase 3: Continuous Delivery

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.

Read More

Load Testing Execution Phase 2: Benchmarking and Complex Cases

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.

Read More

Load Testing Execution Phase 1: Validation and Test Configuration

As an engineer — or anyone in the working world these days — you have roughly one million things on your mind at a time.

So, we realize that after you’ve made the decision to load test with Load Impact (great choice, btw), that you might be interested in our 25+ years of load testing experience when it comes to getting started.

We recommend a three-phase process that you and your team will be able to manage pretty easily, and we’re going to outline each of those phases over the next three weeks in a mini-series of blog posts.

Read More

Posts by Topic

see all