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

### What is integration testing?

This is a testing technique where individual components are tested in a sequence or as a group.

In a complex software system, there are multiple microservices interacting with each other. Each of them is developed to solve a specific use case and allows for multiple interfaces to interact with each other.

As part of the load testing, the entire sequence of APIs will be called in the same sequence for users at the given load configuration.

### Sample simulation

In this scenario, we are simulating and automating the integration flow for a single service.

#### Steps involved

The integration flow contains the following steps:

# What is integration testing?

This is a testing technique where individual components are tested in a sequence or as a group.

In a complex software system, there are multiple microservices interacting with each other. Each of them is developed to solve a specific use case and allows for multiple interfaces to interact with each other.

As part of the load testing, the entire sequence of APIs will be called in the same sequence for users at the given load configuration.

# Sample simulation

In this scenario, we are simulating and automating the integration flow for a single service.

## Steps involved

The integration flow contains the following steps:

Study an example scenario containing multiple APIs that form an end-to-end integration test for load testing.

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

Example 2 - Integration Load Test Simulation

What is integration testing?

Sample simulation

Steps involved