Most people know they need to set goals to improve some part of their life. It helps you avoid wasting energy and make measurable progress. While this is common knowledge, most of us still don't take the time to set goals or measure their progress toward them over time. The result is missed opportunities.
Same thing with the performance testing process – goal setting is a critical step. If you don't set goals, it's impossible to know what defines 'good' or 'acceptable' performance levels. It's equally important to make sure the goals you’ve set are well-informed by both people and data to avoid setting the wrong goals for a given project.
Read how to best define performance testing goals for your organization.
Use this checklist as a reference when evaluating different load testing metrics that you may want to consider when setting goals.
- Average Response Time
The average time that it takes for a request to move from the client to the server and the response to move from the server to the client.
- Peak Response Time
The longest response time that occurs within a given performance testing cycle, which represents the ‘worst case scenario’.
- Error Rate
The percentage of errors that occur during a given performance testing cycle.
- Concurrent Users
The number of users that are active at any given point in time during a performance test, which simulates real potential load situations.
The number of kilobytes per second that’s transmitted during a performance test cycle, which illustrates the amount of data going back and forth.
Ready to start performance testing? Sign up for your free 14-day LoadNinja trial today.