Step-up Performance Test
What is Step-up Performance Test?
The step-up performance test is useful for determining how well a software system performs under various loads. The step-up test, in contrast to the load test, includes a number of stable states in a single test. This test is also known as a “Multi-level Load Test” since it involves various stable
states. Step-up testing begins with fewer users, maintains the same load for a while, and then ramps it up to the next level. At the following load level (step), the test resumes for a predetermined amount of time before moving on to the following level.
In general, a new application can use the Step-up performance test technique, especially if the customer or project team does not provide any non-functional requirements. In the absence of NFRs, a performance tester may quickly determine how well the application performs under various user loads and present the findings to the customer.
How to determine the Step-up Load?
For Existing Application: The step-up test has a very clear goal. The NFRs document may not specifically include the step-up load test as it is not a required test. In this situation, create a workload model that starts with fewer users and increases beyond the stress-test load. In the step-up test under a high load, the likelihood of hitting a break-point is substantial.
For New Application: The step-up strategy is the ideal choice if the application is new and the customer is unaware of performance testing data. because a performance tester is unaware of how the program behaves. The program might fail with 10 users or possibly succeed with 5000 users. Consider how many tests he has to do if he runs separate load tests that last an hour each and adds 100 more users to each test. He could be late for delivery, thus a step-up load test is a preferable choice in this situation.
Purpose of Step-up Performance Test:
- In the case of a new application when NFRs are not defined, evaluate its performance.
- Recognize the application’s behavior under various load levels.
- Test the application’s hybrid performance.
Approach:
The step-up test is a hybrid test that includes load, stress, and break-point testing features. But keep in mind that the step-up exam cannot take the place of these performance assessments since they have different goals.
For both new and old applications, the step-up testing methodology is the same. Performance testers should be aware of or make decisions on the height of the step (User load at each step), the number of steps, and the steady-state time while designing the workload model.
Steady State Duration: Ideal timing is between 10 and 30 minutes rang.
No. of Steps: It depends on the length of the test and the steady-state period.
- Height of the step (User load): Decide as per the expected load. If the expected load is high like more than 1000 then keep the user load around 100 to 200 per step.
A performance tester prepares a workload model for a step-up test with the below inputs:
The height of the step: 50
No. of Steps: 6
Steady-state: 10 mins
Another potential scenario is when a performance tester is unaware of the maximum user load. In this situation, an open-mouth workload model that functions as a break-point test may be created. Look at the graph below:
