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)


We can automate a lot of things and integrate JMeter with other tools.

We will see some examples of automation in this section.


The source code given in the examples has been deliberately simplified to make reading it more enjoyable.

Furthermore, we do not follow best practices (for instance, injectors and tested applications are running on the same server). In the real world, you should replace in OS Process Sampler simple commands by remote ssh calls.

Example 3: Non-Regression Testing of Memory Consumption with EJ JProfiler

In Chapter 7, Load Testing a Website, we saw how to use JProfiler during our technical tests. We will continue to use it in other technical tests, all in an automated way.

We want to create memory dumps of our application at the start of our test and at the end.

This will allow us to ensure that the new version of the tested application does not consume too much memory compared to the old version.

  1. To check this, we will compare the dumps of the two versions...