Book Image

Gatling Fundamentals for Stress Testing APIs - Scala [Video]

By : James Willett Ltd.
5 (1)
Book Image

Gatling Fundamentals for Stress Testing APIs - Scala [Video]

5 (1)
By: James Willett Ltd.

Overview of this book

In this focused guide, we will dive into the world of Gatling, the potent open-source tool for web application load-testing. Starting with Gatling installation, we will uncover the power of Gatling Recorder, perfect for capturing user journeys and transforming them into scripts effortlessly. We will start by executing our first Gatling script and gain insights from the application through testing. This will be followed by core topics such as adding pauses, checking response codes, examining response bodies, and data extraction; we will then master debugging session variables and code reuse techniques. Moving ahead, we will dive into advanced topics such as looping HTTP calls, authentication and working with CSV feeders. We will understand basic and complex custom feeders, as well as templating files. We will introduce load simulations, ramping up users, and running Gatling from the command line with runtime parameters. Throughout the course, we will tackle challenges, refine our skills, and learn to monitor test executions with Gatling test result reports. We will also guide you on integrating Gatling into CI pipelines, covering GitHub repositories, Jenkins setup, and Travis CI configuration. By the end, you will be a Gatling expert, capable of effectively load-testing web applications and seamlessly integrating Gatling into CI/CD workflows, ensuring optimal performance and reliability.
Table of Contents (10 chapters)
Free Chapter
1
Introduction to Gatling
Chapter 10
Gatling with Continuous Integration Tools
Content Locked
Section 4
Jenkins First Gatling Test
In the previous video, we successfully installed Jenkins and configured the Gatling plugin. After installing the plugin, we chose to restart Jenkins to ensure proper integration. Once Jenkins restarts, you will find yourself back at the login screen. At this point, it's essential to enter the credentials for the test user we created earlier. If you recall, the username was "test user" and the password was simply "password". Entering these details will grant us access to our Jenkins server.