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

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

Performance Testing Best Practices: User Scenarios

Most engineers new to load testing first ask, “How many concurrent users am I expecting to hit my website/app/API?”

This isn’t far off from a proper starting point, but based on our more than 2 million performance tests, we recommend you put aside total traffic numbers for a minute and think about what you expect users to actually do.

That’s because user scenarios are the cornerstone of your load test. To put it simply: Detailed, realistic user scenarios mean your load tests will produce actionable data you can use to optimize your websites, apps, APIs and infrastructure.

So, let’s explore user scenarios and share some best practices.

Read More

Performance Testing Tips: Client Sleep Time

In order to get actionable results from your performance tests, you need to create scenarios that closely mimic the expected behavior of your users.

After all, what good is a test if it’s not preparing you for a real-world event?

Whenever a user stops taking actions in order to think about their next move in an application, that translates to “client sleep time” in your user scenario — and it’s an incredibly important, yet often-forgotten function.

Read More

Improving the Script Editor Ergonomic

Tl;dr — We have redesigned the user scenario editor to create a better scripting experience in our web app. You could also use your own editor of choice with the Load Impact CLI. The focus in the Developer Experience (DX) is to create a productive platform for performance testing.


Read More

The Load Impact CLI

tl;dr — We’ve released the beta version of the Load Impact CLI, which is focused on manipulating user scenarios.

  • Users can create, update, save, delete and validate user scenarios from the command line
  • A group of users asked for this, and you can ask for stuff, too. Our Support team is always taking suggestions
  • This is just the first iteration (of course), so your input is valuable and very welcome. Contact us on Twitter or LinkedIn

Read More

Load Testing the Scalability of Your App & Infrastructure

Read More

What to Look for in Load Test Reporting: Six Tips for Getting the Data you Need

Read More

New Load Script APIs: JSON and XML Parsing, HTML Form Handling, and more!

Load scripts are used to program the behavior of simulated users in a load test. Apart from native functionality of the Lua language, load script programmers can also use Load Impact's load script APIs to write their advanced load scripts.

Read More

Configuring a load test with multiple user scenarios

We recently had a great question come in from one of our customers that we thought we would share.

Read More

Posts by Topic

see all