Book Image

Master Apache JMeter - From Load Testing to DevOps

By : Antonio Gomes Rodrigues, Bruno Demion (Milamber), Philippe Mouawad
Book Image

Master Apache JMeter - From Load Testing to DevOps

By: Antonio Gomes Rodrigues, Bruno Demion (Milamber), Philippe Mouawad

Overview of this book

Load tests help identify the maximum number of requests a software system can handle. One popular open source tool for load testing is JMeter. By leveraging the features and capabilities of JMeter, you can perform extensive load testing and fix issues in your application before they become problematic. This book is written by JMeter developers and begins by discussing the whole process, including recording a script, setting it up, and launching it, enabling you to almost immediately start load testing. You'll learn the best practices that you must follow while designing test cases. You'll also explore the different protocols offered by JMeter through various real-world examples. Finally, you'll see how to integrate JMeter into the DevOps approach and create professional reports. You'll discover ways to use the eco-system of JMeter to integrate new protocols, enrich its monitoring, and leverage its power through the use of the cloud. By the end of this book, you'll know all that's needed to perform comprehensive load testing on your applications by using all the best practices and features of JMeter.
Table of Contents (14 chapters)


Let's look at some best practices that will allow us to achieve successful load test campaigns.

The first step is to define our test plan to limit the scope and goals of the test campaign. Depending on the desired goals, you need to make different choices.

Some will impact scripting (datasets, and so on); others will impact the type of test (soak tests, stress tests, and so on) to be performed. The number of tests will also be impacted (the addition of technical tests and so on).

Studying and understanding the architecture of the system will have a big impact on the scripts.

For example, if the static resources (images, CSS files, and so on) are hosted outside the tested system (for example, on a Content Delivery Network (CDN)), there is no need to include them in our scripts.

We can exclude them when we record our scripts using the Request Filtering tab of HTTP(S) Test Script Recorder:

Figure 7.17: HTTP(S) Test Script Recorder


This is done by default if you...