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)

Setting Up Shift-Left Strategy

In load testing, Shift-Left would result in:

  • Early load tests across project phases, particularly in the development and testing phases
  • The automation of load tests and integration in the build pipeline

Still, Shift-Left is not that easy for many reasons:

  • The ability to load test depends, at minimum, on the environment and the availability of test data. As we have seen in previous chapters, data has a huge impact on load test quality.
  • The ability to automate load tests depends, at minimum, on the availability of environments, the automation cost (which depends on the application architecture), and the ability to mock third parties.
  • Return of investment (ROI) of tested features. You may hold that 100 percent of the application should be tested, but that's probably impossible for the majority of applications.

Here are a few examples of how much testing technologies can cost a company (the more "'+"' signs there...