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)

Scoping

In JMeter, elements are organized in a tree, where each node has parents and children, which can be branches or leaves.

The scope of an element is based on where the element is located in the tree branch.

Simply defined, the scope of an element is composed of the elements that are children of its own parent.

In the following screenshot, the scope of Response Assertion, highlighted in red, includes the elements contained in the yellow rectangle; namely, all the child elements of the parent, Test Plan:

Figure 4.1: Scope

As a consequence, when the test is run, it will execute the assertion for every HTTP Request:

Figure 4.2: Scope of Assertion