đź““
Loadium Wiki
  • Welcome to Loadium
  • Getting Started with Loadium
  • Quick Guides
    • Quick Start
    • JMeter Test
    • Locust Test
    • Script Builder
      • Simple HTTP Builder
      • Record&Play
    • Gatling Test
    • WebDriver Test
    • HLS Test
    • Understanding Test Reports
    • Test Execution Fail Reasons
    • File Output
  • ABOUT LOADIUM
    • Features
    • Pricing
    • VUH - Virtual User Hour
  • ACCOUNT
    • Profile & Account
    • Subscription
  • Features
    • Test Report
    • Compare Test
    • Private Location
    • Report PDF Export
  • Test Settings
    • Split CSV
    • Sandbox
    • Multi-Step
    • Geolocation
    • Customize Setup
    • Dedicated IP
    • Send Email
    • DNS Override
    • TPS
    • Network Type
    • Test Scheduling
    • Test Failure Settings
    • JMeter Settings
    • Failure Criteria
    • Flexible Thread Scheduling
  • CONTINUOUS INTEGRATION SUPPORT
    • Azure DevOps Pipeline
    • Jenkins Load Testing with Loadium
  • Integrations
    • Microsoft Teams Integration
    • New Relic Integration
    • AppDynamics Integration
    • TeamCity Integration
  • Jmeter Corner
    • Built-in JMeter Functions
    • How to Install JMeter Plugins
    • Record and Play Load Testing With Jmeter in 5 Steps
    • Websocket with Apache JMeter
    • JMeter Timers
    • Handling Error Messages of JMeter Tests in Loadium
    • Details of Throughput Controller in JMeter (Splitting Threads to Different Requests)
    • How to Add a Varying Number of Parameters in Apache JMeter
    • Local Network Simulation On JMeter
    • Running Load Test with FTP Server
  • Gatling Corner
    • Introduction to Gatling
    • Gatling Recorder
    • Gatling Pros&Cons
  • PUBLIC APIs
    • Get Test Status Service
    • Authentication Service
    • Get Performance Test List Service
    • Start Performance Test Service
Powered by GitBook
On this page
  • 1) Basics
  • 2) Configuration
  • 3) Geolocation
  • 4) Advanced Settings

Was this helpful?

  1. Quick Guides

Gatling Test

A quick guide for creating Gatling test on Loadium

PreviousRecord&PlayNextWebDriver Test

Last updated 2 months ago

Was this helpful?

Gatling is an open-source performance testing framework, which uses Scala, Akka, and Netty as a technology stack and as its backbone. You can upload your previously created Gatling script to Loadium to run tests. You can go to Create Page and choose Gatling Test to start creating a test.

1) Basics

  • Test Name is a mandatory field as it will be referenced in future usage.

  • Project is an optional field that allows you to assign your tests to a specific project in order to group them.

  • Upload File field let you upload a scala file from the upload file area. Whenever a test is saved, newly added files are uploaded to our servers. In case there’s an update, Loadium will automatically update the files by matching them by their file name.

Note: At least one scala file is mandatory to save a Gatling test.

Note: The name of the CSV that you have uploaded and the name of the CSV in your scala file must be the same.

  • Notes: Allows you to enter additional details and self-explanatory notes.

2) Configuration

  • Engine Count: Amount of engines that will be used for the test execution.

  • Users Per Engine: Amount of users (threads) that will be generated from each engine to execute the script.

  • Duration(min): Total time for Loadium to execute Gatling scenarios.

Note: Test run times can not exceed the duration you set but if your Gatling scenario ends the test will be automatically finished.

Sandbox Test: Allows you to run free tests to debug your tests. If you just want to make sure that your system is ready for testing, or your script is properly working, you can enable this option (enabling sandbox test will limit the test configuration).

3) Geolocation

Cloud Services

Loadium allows you to run globally distributed load tests by providing servers. Lets you select regions to execute situational user simulations. When a location is chosen, engines will be generated in that particular region and all requests will come from that region.

You can find more detailed information on the Geolocation page.

Private Location

You can find more detailed information on the Private Location page.

4) Advanced Settings

You can find more detailed information on the Dedicated IP page.

Gatling Version: Choose the Gatling version according to your test script implementation.

Recommended version of Gatling is 3.5.1

Network Type: Loadium lets you choose different network types to simulate network behavior by imitating the bandwidth and network delays. They all have different bandwidth and network delay values. In case nothing is selected, by default Wifi is set to all engines. You can find more detailed information on the Network Type page.

You can find more detailed information on the TPS page.

You can check out the following pages for additional test settings:

Split CSV File: Select this option to split your CSV data into engines uniquely. You can find more detailed information about Split CSV .

Send Email: In case you would like to be notified by e-mail after the test ends, you can enable this feature. You can find detailed information about this feature, .

Instead of provided servers, Loadium allows you to create custom locations with integration to run load tests from your personal servers.

Dedicated IP: If the system that is going to be tested has access limitations such as a firewall or DDoS protection, you can rent static IP’s and whitelist them to allow Loadium to perform a load test on the system. Enabling this option will run the test with the rented dedicated IP’s. To rent dedicated IP’s, please .

Limit TPS: This parameter allows you to limit the total throughput (requests happening per second) of the test’s execution. This limitation works on engines individually, so if you are using “X” amount of engines, the maximum throughput across all engines will be limited to X * Limit Value. You can find more detailed information about TPS .

here
here
Geolocation
Docker
Private Location
contact our support
Dedicated IP
Network Type
here
TPS
Failure Criteria