Use Eclipse to edit and manage a Gatling project, then run the tests with its Maven or Gradle wrapper. Gatling’s current documented workflow is build-tool based; you do not need a dedicated Eclipse plugin or an Eclipse-native Gatling run button.
Check the prerequisites
- Install a 64-bit OpenJDK LTS release in Gatling’s supported 11–25 range. Gatling recommends Azul JDK in its installation guide.
- Use Maven 3.6.3 or later, or Gradle 7.6 or later. You can avoid a global build-tool installation by using the wrapper included in an official starter project.
- Check the Java runtime available to your terminal with
java -versionand Maven withmvn -version. Gatling launch scripts and the Maven plugin honorJAVA_HOME; a runtime mismatch can produce anUnsupported major.minor versionerror. - Choose a current Gatling version from the official starter project. Version numbers change, so check the starter rather than relying on an old version number in a tutorial.
Create and import a Gatling project
- Download or clone the official Gatling Maven Java starter. It includes a Maven Wrapper, which runs the project with
./mvnwon macOS or Linux andmvnw.cmdon Windows. - In Eclipse, select File → Import → Maven → Existing Maven Projects. Browse to the project folder containing
pom.xml, complete the import, and allow Eclipse to resolve dependencies. - Keep the starter’s Maven directory layout. Java simulations normally go in
src/test/java. Put feeders, request templates,gatling.conf, and other non-source resources insrc/test/resources; Maven puts these resources on the test classpath. - If you want to write simulations in Scala, start with Gatling’s Scala Maven starter. Current Gatling Maven plugin version 4 and later does not compile Scala by itself; use the starter’s
scala-maven-pluginconfiguration.
Write a basic simulation
A simulation is the class Gatling launches. It must register its workload by calling setUp exactly once. This Java example sends one request to a placeholder host; replace the host and path with an endpoint you are authorized to test.
import io.gatling.javaapi.core.*;
import static io.gatling.javaapi.core.CoreDsl.*;
import io.gatling.javaapi.http.*;
import static io.gatling.javaapi.http.HttpDsl.*;
public class BasicSimulation extends Simulation {
HttpProtocolBuilder httpProtocol = http.baseUrl("https://example.test");
ScenarioBuilder scn = scenario("Basic").exec(http("request").get("/"));
{
setUp(scn.injectOpen(atOnceUsers(1))).protocols(httpProtocol);
}
}Use the DSL syntax and imports that match the language and Gatling release in your starter. Avoid naming the class with a name that begins with Test, because Maven Surefire may treat it as a conventional unit-test class.
Run the simulation from Eclipse
Save your changes in Eclipse, then open its integrated Terminal or an external terminal at the Maven project root. Run the Maven wrapper:
Recommended Free Tools
# macOS or Linux
./mvnw gatling:test
# Windows
mvnw.cmd gatling:testIf the project contains multiple simulations, the Maven plugin prompts you to select one. To choose deterministically, pass the simulation’s fully qualified class name, including its package:
./mvnw gatling:test -Dgatling.simulationClass=computerdatabase.ComputerDatabaseSimulationThe package declaration in the class must match its directory path. The official first simulation tutorial uses example.BasicSimulation when prompted, then directs you to open the generated report.
Open the report
When the run finishes, use the report path printed in the terminal. Reports are written below target/gatling, usually in a timestamped directory; open that run’s index.html in a browser.
Run the HTTP Recorder
From the Maven project root, start the Recorder with the Maven plugin:
# macOS or Linux
./mvnw gatling:recorder
# Windows
mvnw.cmd gatling:recorderKeep configuration and other classpath-based files in src/test/resources so the build tool can make them available to Gatling.
Fix common Eclipse setup problems
Gatling imports are unresolved
Refresh the Maven project in Eclipse so it resolves dependencies again. Confirm that the project uses a supported 64-bit OpenJDK version and that the Maven dependencies have completed downloading.
Rank #4
The terminal works, but Eclipse uses a different Java version
Compare the terminal’s java -version and JAVA_HOME with the JDK configured for the Eclipse project. Align them, then refresh the Maven project and rerun the wrapper.
A Scala simulation does not compile
Check that the project uses the Scala compiler setup from the official Scala Maven starter. The Gatling Maven plugin alone is not sufficient to compile Scala in current version-4 configurations.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Best Value
The selected simulation cannot be found
Verify the simulation’s package declaration, its source directory, and the fully qualified name supplied to -Dgatling.simulationClass. For example, a class declared in package computerdatabase must be selected as computerdatabase.ComputerDatabaseSimulation.
You are following an old Eclipse installation guide
Use the current Maven or Gradle starter and import it into Eclipse. Gatling’s current official setup guidance is centered on build tools, not on legacy standalone bundles or a dedicated Eclipse integration.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Choose Maven or Gradle for your project
Both build tools can serve as the execution layer while Eclipse remains your editor. Prefer the one that fits your team’s existing builds and CI/CD pipeline. Check the starter projects for the language you plan to use, whether the wrapper fits your environment, and how your pipeline will retain or publish Gatling reports. For the Maven Java workflow described above, the starter supplies a wrapper and uses the Maven plugin to run simulations.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
