Gain insights into Gatling fundamentals, delve into advanced scripting, simulate network conditions with puppeteer and lighthouse, and set up Jenkins CI for scalable performance testing automation.

performance.tar.gz

Puppeteer

Gatling-1

Java

shell

Lighthouse

gatling-spa-run-framework

gatling-spa-run-framework-copy

Gatling

gatling-local-server

gatling-local-server-live

Almost every company in the world needs to test its scalability and performance of their products or applications.

In this course, you will learn the fundamentals of Gatling, an open-source performance testing tool that is in great demand in the software industry. You will start by learning the basics of performance testing including scalability testing and stress testing.

You will then move on to more advanced concepts such as writing Gatling scripts, understanding web page performance and simulating network throttling using puppeteer and lighthouse tools.

Lastly, you will learn to set up Continuous Integration (CI) using Jenkins for Gatling which will be useful for running tests remotely. By the end of this course, you will have some new great skills for your resume.

Performance Test Automation 101: Gatling, Lighthouse, & Jenkins

Gatling provides various features to programmatically control the simulation and flow of execution. Its features are listed below:




### Scenarios

Scenarios represent the user behavior containing multiple action blocks, and each action block has its own course of execution and constructs.

### Checks
Checks verify the received response from the server and saves it in the user session for reuse.

### Loops

Gatling provides various loops that allow us to run a chain of actions multiple times, such as `repeat`, `foreach`, `during`, `asLongAs`, `doWhile`, `asLongAsDuring`, `doWhileDuring`, and `forever`.

### Conditional statements

Gatling provides various loops that allow us to selectively run a certain chain of actions, such as `doIf`, `doIfEquals`, `doIfOrElse`, `doIfEqualsOrElse`, `doSwitch`, `doSwitchOrElse`, `randomSwitch`, `randomSwitchOrElse`, `uniformRandomSwitch`, and `roundRobinSwitch`.


### Error handling

Gatling provides us with ways to gracefully handle the error and retry the chain of actions on failure using constructs, such as `tryMax`, `exitBlockOnFail`, and `exitHereIfFailed`.  

### Throttling

Gatling allows us to throttle the requests hit from the client and simulate a more realistic way of making requests. It allows us to configure requests both at the global and scenario levels.

### Feeders

Gatling provides us with various ways to feed data to the simulation using methods, such as `Continuous iterator`, `Implicit feeder`, file-based feeders like `JSON` and `CSV feeders`, `JDBC feeder`, and `Redis feeder`.

### User injection profiles

Gatling allows us to inject a user and simulate the load on environment using strategies like `atOnceUsers`, `constantUsersPerSec`, `rampUsers`, `heavisideUsers`, `rampUsersPerSec`, `nothingFor`, `incrementUsersPerSec`, `constantConcurrentUsers`, `rampConcurrentUsers`, and `incrementConcurrentUsers`. 

### Assertions

Gatling allows us to assert the response times and count the number of failed requests. It helps us to keep check on the overall health of the simulation. Any failure in assertion causes the build to exit with a non-zero value.


### Web sockets

Gatling provides a way to load test web sockets and make HTTP requests.

We will see each of these features in detail in the coming lesson.

# Scenarios

Scenarios represent the user behavior containing multiple action blocks, and each action block has its own course of execution and constructs.

# Checks
Checks verify the received response from the server and saves it in the user session for reuse.

# Loops

Gatling provides various loops that allow us to run a chain of actions multiple times, such as `repeat`, `foreach`, `during`, `asLongAs`, `doWhile`, `asLongAsDuring`, `doWhileDuring`, and `forever`.

# Conditional statements

Gatling provides various loops that allow us to selectively run a certain chain of actions, such as `doIf`, `doIfEquals`, `doIfOrElse`, `doIfEqualsOrElse`, `doSwitch`, `doSwitchOrElse`, `randomSwitch`, `randomSwitchOrElse`, `uniformRandomSwitch`, and `roundRobinSwitch`.


# Error handling

Gatling provides us with ways to gracefully handle the error and retry the chain of actions on failure using constructs, such as `tryMax`, `exitBlockOnFail`, and `exitHereIfFailed`.  

# Throttling

Gatling allows us to throttle the requests hit from the client and simulate a more realistic way of making requests. It allows us to configure requests both at the global and scenario levels.

# Feeders

Gatling provides us with various ways to feed data to the simulation using methods, such as `Continuous iterator`, `Implicit feeder`, file-based feeders like `JSON` and `CSV feeders`, `JDBC feeder`, and `Redis feeder`.

# User injection profiles

Gatling allows us to inject a user and simulate the load on environment using strategies like `atOnceUsers`, `constantUsersPerSec`, `rampUsers`, `heavisideUsers`, `rampUsersPerSec`, `nothingFor`, `incrementUsersPerSec`, `constantConcurrentUsers`, `rampConcurrentUsers`, and `incrementConcurrentUsers`. 

# Assertions

Gatling allows us to assert the response times and count the number of failed requests. It helps us to keep check on the overall health of the simulation. Any failure in assertion causes the build to exit with a non-zero value.


# Web sockets

Gatling provides a way to load test web sockets and make HTTP requests.

We will see each of these features in detail in the coming lesson.

Introduction

Basics of Performance Testing

Gatling: Load and Stress Testing Tool

Gatling: Script Features

Examples: Simulations Using Gatling

Web Page Performance

Network Throttling

Download Custom Gatling Test Framework

Gatling with Jenkins

Conclusion

About Gatling's Script Features

Scenarios

Checks

Loops