Few Things to consider before Load Testing
- Number of Concurrent Users
- Test Duration
- Setting up Ramp-Up Period.
- Simulating real user-test scenarios
- With proper think time and delays
- Geo-Distributed virtual loads.
- What metrics we will track
- Analyzing captured Data.
No need to read further, if are interested in knowing more about above terms , you can continue reading
1. Targeting the Right Workload
- On average, how many operations occur in a typical hour. How about at peak?
- What is the goal of this test? → what do we want to measure
- What does your server or database activity typically look like?
- When choosing tasks to emulate, are you focusing on the ones that are the biggest risk to your business?
- How heavy if a load do you really need?
- What metrics will you track or are required
It’s not enough just to create a test that will mimic real-world scenarios. You also need to ensure that your scripts are not overloading the test tool itself.
Make sure you have optimized the settings for your test scenario. Time, duration of run, monitors selected and amount of info logged — any of these can put stress you’re your tool.
4. Think Time
Think time is useful to mimic the right workload according to the real behavior of the virtual user. Just like a functional Selenium test, it’s also advised to use think time rather than a sleep function.
Use think time instead of sleep function, every tool has this functionality.
5. Ramp Up and Ramp Down Time
It’s probably unnatural for an application to get so many virtual users logging in at the same time and out at the same time.
6. Monitoring and Diagnostics
Monitoring and diagnostics also need to be taken into consideration when it comes to large-scale load tests.
- Only measures those parameters that are useful to you.
8. GUI Virtual Users
What happens when you’re going to run GUI virtual users?
Typically, GUI virtual users, as opposed to HTTP-level virtual users, consume more resources like memory and GDI resources.
GUI users are heavier virtual users, and their footprint is more substantial. It’s critical to know how many GUI users you can run on your load generator.
You should be ready in advance to avoid redundant failures and to prepare the right amount of load generators, balancing the workload across them.
9. Analyze Test data
Don’t jump to conclusions without properly analyzing the data. It takes experience and skill to extract relevant conclusions from the data produced by a load test, so don’t take this step lightly.