Checklist of Performance Testing Best Practices

  September 03, 2019

Performance testing is becoming an increasingly important part of the DevOps process. While most load tests targeted servers in the past, the rise of cloud computing has made it possible to test client-side performance with real browsers. The combination of client and server performance tests simplify the debugging process and provide better insights.

Below is a checklist of performance testing practices to refer to:

  • Identify the Business Case
    What are the business requirements for the application’s performance? You don’t want to waste time running extreme tests for an application that will experience comparatively little traffic (e.g. an internal application) or vice versa for a high-traffic app.
  • List the Relevant KPIs
    What are the key performance indicators that you care most about? For example, you may be concerned with average response times, peak response times, peak concurrent users, or a combination of those metrics.
  • Choose the Right Tool
    There are many different load testing tools and the right choice depends on your organization. If you prefer a code-heavy solution, then Gatling may be a better option than JMeter for your infrastructure load tests.
  • Scale Up Users Over Time
    Start with a small number of users and then scale them up over time. The goal isn’t to break the server; rather, you should seek to identify bottlenecks that start to emerge when a peak number of users approaches.

Don’t Forget the Client
Client-side JavaScript and HTML can have a significant impact on performance, which makes real browser testing invaluable. LoadNinja is a great option for these kinds of tests given its ease of use.

Try out LoadNinja for free for 14-days now.