Gatling’s low-code tools bridge the gap between existing API specifications and load test scripts. Instead of writing every HTTP request by hand, you can import a Postman collection you already maintain or record a real browser session and let Gatling generate the simulation structure for you. The result is a fully editable Gatling simulation that you can enrich with checks, feeders, and custom injection profiles. This page covers two workflows: importing a Postman collection using theDocumentation Index
Fetch the complete documentation index at: https://mintlify.com/gatling/gatling.io-doc/llms.txt
Use this file to discover all available pages before exploring further.
@gatling.io/postman package, and recording a browser session using the Gatling Recorder or Gatling Studio.
Postman Collection Import
The Gatling Postman component lets you load a Postman collection JSON file directly into a simulation. This reduces test authoring time, keeps your functional and load test definitions consistent, and improves collaboration between developers, QA, and operations teams who already maintain Postman collections.Supported Features
Most core Postman request features are supported. The following items are currently limited or not yet available:- Postman Cloud integration — collections must be exported as JSON files; direct cloud sync is not supported
- Pre-request and post-response scripts — script execution is not supported
- Dynamic variable handling — modifying variable values at runtime is not supported
- Randomly generated data — Postman’s
{{$randomXxx}}dynamic variables are not supported - File uploads — supported by placing files in your project’s
resourcesfolder
Step-by-Step: Import a Postman Collection
Get a Gatling JavaScript Project
Export Your Postman Collection
- Open the collection you want to use for load testing.
- Click the … (three-dot) menu next to the collection name.
- Select Export.
- Choose Collection v2.1 format and click Export.
- Save the resulting
.jsonfile.
Add Collection Files to Your Project
resources folder:Write the Simulation
src/ with the .gatling.js extension. The simulation has three parts: imports, a scenario built from the Postman collection, and an injection profile.Run the Simulation Locally
target/gatling/.Deploy to Gatling Enterprise (Optional)
.zip file in target/. Upload it via Packages in the Gatling Enterprise console, then create a simulation pointing to it.Automated deployment (Configuration as Code):Browser Recorder
The Gatling Recorder is a proxy-based tool that intercepts HTTP traffic from your web browser and converts it into a Gatling simulation. It is included with every Gatling installation and supports both Java/Maven and JavaScript/npm projects.Step-by-Step: Record a Browser Session
Clone the Demo Project and Configure Prerequisites
https://ecomm.gatling.io. Clone the demo project and navigate to your preferred SDK directory:- Java / Maven
- JavaScript / npm
Launch the Recorder
- Java / Maven
- JavaScript / npm
| Setting | Value |
|---|---|
| Recorder Mode | HTTP Proxy |
| Package | example |
| Class Name | RecordedSimulation |
| Follow Redirects? | ✅ Checked |
| Infer HTML Resources? | ✅ Checked |
| Automatic Referers? | ✅ Checked |
| Remove Cache Headers? | ✅ Checked |
| No Static Resources | ✅ Clicked |
| Format | Java 17 (or JavaScript) |
Record the User Session
| Button | Action |
|---|---|
| Add | Insert a tag to label a group of actions (e.g. “Homepage”, “Login”) |
| Clear | Clear all captured events |
| Cancel | Abort the recording |
| Stop & Save | Finish and write the simulation file |
- In the Recorder, add the tag Homepage, then navigate to
https://ecomm.gatling.io. - Add the tag Authentication, then click the Login button and submit the form.
- Add the tag Cart, then click Add to cart for a product.
- Click Stop & Save in the Recorder.
Inspect the Generated Simulation
- Java
- JavaScript
src/test/java/example/RecordedSimulation.java- Adding
.check(status().is(200))to requests - Extracting dynamic values with
.check(jsonPath("$.token").saveAs("authToken")) - Replacing hardcoded credentials with feeder-supplied values
Gatling Studio (Desktop Recorder)
Gatling Studio is a native desktop application that records browser sessions and exports a ready-to-run Gatling project. It is available for macOS, Windows, and Linux.Download and Install Gatling Studio
Log In and Set Up a Workspace
- Open Gatling Studio.
- Click Log in with Gatling Enterprise Edition account.
- Complete authentication in the browser window that opens, then return to the Studio.
- Set your workspace — a local folder where recordings, scenarios, and exported projects are stored.
Record a Journey
- Click Record a journey on the Recordings page.
- Select your Chromium-based browser from the detected list (or provide a path).
- Enter the URL you want to test and click Start the recording.
- Browse through the user journey you want to simulate.
- Close the browser when done. Studio saves the recording as a HAR file in your workspace.
Create a Scenario from the Recording
- Open the recording in Studio to view its captured requests.
- Click Create a scenario from recording.
- In the scenario filter, select which domains to include and whether to include static resources (static resources are generally not recommended for load testing).
- Click Save.
pause() calls between groups based on recording timing.Export as a Gatling Project
- From the scenario view, click Export project.
- Studio generates a complete Java/Maven project pre-loaded with your scenario.
- Open the exported project in your IDE, customize it as needed, and run it with
./mvnw gatling:test.
Sec-* headers are filtered out automatically during export since they are not relevant in load testing contexts.