Comment on page
Gatling Test
A quick guide for creating Gatling test on Loadium
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.
- 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.
Split CSV File: Select this option to split your CSV data into engines uniquely. You can find more detailed information about Split CSV here.
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.
- 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, here.
- 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).
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.
Instead of provided servers, Loadium allows you to create custom locations with Docker integration to run load tests from your personal servers.
You can find more detailed information on the Private Location page.
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 contact our support.
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.
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.
You can find more detailed information on the TPS page.
If you don't see the answer to your question here, please reach out to us to let us know! We're always improving our documentation.
Happy testing!
Last modified 1yr ago