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)

Identify Critical Business Scenarios to Script

If the business scenarios are not identified well, the tests will not conform to what will happen during production, and will therefore be useless, or even dangerous, giving the false impression that the targeted platform handles the load without problems.

It is therefore critical to identify the relevant business scenarios and weight them.

To define these scenarios, we can:

  • Retrieve the statistics of the application if they exist (for example, the daily or monthly number of business transactions, an analysis of web statistics (access log, analytics tools...), and so on)
  • Define them with Users/Business User/Product Owner

For the number of scenarios, it is advisable to apply the Pareto Principle (, also called the 80/20 rule, and therefore to take (at least as a first step) only the 20% of scenarios that cover 80% of the scope of the application – for example, by not simulating different...