Concept

There are some concepts in the Gatling. They are as follows:

Virtual User

deal with logic between requests
  each one having its own data and maybe taking a distinct browsing path
  implements
      other tools implement those virtual users as threads
      Gatling implements them as messages
          scales much better and can deal easily with thousands of concurrent users

Scenario

represent users’ behaviors
   represented as scripts in conjunction with a DSL

Simulation

 A simulation is a description of the load test

Session

  Those Sessions are the actual messages that go down the scenario workflow

Feeders

 Feeders are a convenient API for testers to inject data from an external source into the virtual users’ sessions.

Checks

 A check is a response processor that captures some part of it and verifies that it meets some given condition(s). 
    Checks can also be used to capture some elements and store them into the Session so that they can be reused later, for example to build the next request.

Assertions

 Assertions are used to define acceptance criteria on Gatling statistics

Reports

 By default, reports are automatically generated at the end of a simulation. 
    content
        Indicators
        Active users over time
        Response time distribution
        Response time percentiles over time
        Requests per second over time
        Responses per second over time

Configuration

Configuration files

logback.xml
gatling.conf

Command Line Options

$JAVA_OPTS

1	JAVA_OPTS="myAdditionalOption" bin/gatling.sh

How to setup develop environment in local

I will use IntelliJ as an example as follows:

Use Maven Arch

This blog is under a CC BY-NC-SA 3.0 Unported License
Link to this article: https://younggod.netlify.app/2020/05/08/tech/Test/Gatling/