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)


Nowadays, time to market is critical, and we have several solutions to reduce it:

  • Agile methods
  • Minimum Viable Product (MVP)
  • DevOps, etc

Load testing must support these changes. As a consequence, we need to test earlier and often.

The first point to consider is that the earlier the tests are performed, the better it is.

Indeed, a bug discovered early in a project life cycle:

  • Is easier to fix since it is ideally fixed within the development phase. Fixing a bug during the integration phase means digging into more layers to find the root cause, which leads to higher costs.
  • Costs less than a production bug, as it does not impact customers. Think of a bug on pricing as an illustration.

The second point to consider is that tests must be performed at all stages of the application's life cycle: from development to integration, to production.

This approach of testing earlier is called Shift-Left, and it can naturally be applied to load testing.

To reach these...