The no-code test builder lets you design and launch a full load test entirely within the Gatling Enterprise Edition web interface. You define the HTTP requests, choose an injection profile template, configure your load generator locations, and optionally set acceptance criteria—all through guided forms, without writing or packaging any simulation code. This makes it ideal for quick validations, exploratory testing, and teams who are just getting started with performance testing.Documentation 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.
Creating a no-code test
Open the test creation modal
In the Tests view, click Create a test. If the Tests view is empty, click Get started with no-code tests. The creation modal opens.Select No-code from the three available options, then click Create.
Name your test (optional)
Enter a display name for your test. If you leave this blank, Gatling Enterprise generates a default name automatically. You can rename the test at any time from the kebab menu in the tests table.
Build your user scenario
The scenario editor lets you chain together HTTP requests that make up a single virtual user’s journey.For each request:
Use the Add request button to append additional steps to the scenario. To reorder or remove a request, use the controls beside each entry.Inter-request pausesClick the Optional: configure pauses accordion to add think-time between requests. Enter the pause duration in seconds. Pauses simulate realistic user behaviour—browsing, reading, deciding—between interactions.
| Field | Description |
|---|---|
| Method | HTTP verb: GET, POST, PUT, DELETE, PATCH, HEAD, or OPTIONS |
| URL | The full URL the request is sent to |
| Request body | Optional request payload (for POST, PUT, PATCH) |
Select an injection profile
Choose from three injection profile templates. Each template pre-configures a different load shape:
- Capacity Test
- Stress Test
- Soak Test
Simulates a progressively growing user load to find the system’s maximum capacity. The virtual user arrival rate ramps from an initial value up to a final value over the test duration.Parameters to set:
- Test duration
- Initial user arrival rate (users/second at the start)
- Final user arrival rate (users/second at the end)
Configure load generator locations
Choose where Gatling Enterprise will start your load generators. The no-code builder defaults to 1 load generator in the Europe (Paris) region.For each location you add:
- Managed Locations
- Private Locations
- Dedicated IPs
Managed load generators are operated by Gatling in 11 global regions. Each instance provides:
- CPU: 4 cores
- RAM: 8 GB
- Network: up to 10 Gbit/s
- AP Pacific (Hong Kong)
- AP Pacific (Tokyo)
- AP Pacific (Mumbai)
- AP SouthEast (Sydney)
- Europe (Dublin)
- Europe (London)
- Europe (Paris)
- SA East (São Paulo)
- US East (N. Virginia)
- US West (N. California)
- US West (Oregon)
| Field | Description |
|---|---|
| Location | Geographic region for load generator placement |
| Number of load generators | Number of parallel instances in this region |
| Weight distribution | Optional — assign a percentage of total load to each location (all weights must sum to 100%) |
When using private locations or dedicated IPs, ensure that your load generators have network connectivity to the target application.
Apply optional configurations
Expand any of the optional sections in the configuration wizard to further tune your test.
Acceptance criteria
Acceptance criteria
Define pass/fail thresholds for key performance indicators such as response time percentiles and error rate. No-code acceptance criteria are configured through the UI; for test-as-code tests these are defined in the simulation code using the Gatling assertions API.
Time window
Time window
Exclude warm-up and cool-down periods from acceptance criteria and SLO calculations.
| Field | Description |
|---|---|
| Ramp Up | Seconds to exclude from the start of the run |
| Ramp Down | Seconds to exclude from the end of the run |
Stop criteria
Stop criteria
Automatically end the run if a monitored metric exceeds a threshold for a sustained period. Configure:
Example: stop the run if the global error ratio exceeds 5% for the last 30 seconds.
| Field | Description |
|---|---|
| Metric | Mean CPU usage, Global error ratio, or Global response time (at a specific percentile) |
| Threshold | The ceiling value that triggers the stop condition |
| Timeframe | How long (in seconds) the metric must stay above the threshold |
Managing no-code tests
No-code tests appear in the same Tests view as test-as-code tests and support the same management operations via the kebab menu (⋮):Edit test
Reopen the no-code builder pre-filled with the existing configuration.
Duplicate test
Clone the test to iterate on variations without affecting the original.
Copy test ID
Copy the test UUID for use in API calls or CI automation.
Delete test
Permanently remove the test configuration. Historical runs are not deleted.
Organization administrators can disable no-code simulations for an entire organization in Organization Settings. When this feature is disabled, no new no-code tests can be created and existing no-code tests cannot be launched.