results: where test results are generated.

When running on Gatling Enterprise, they are packaged in a single “fat JAR” file together with your Simulations code.

lib: you can add you own dependencies (JAR files) here.

resources: non source code files such as feeder files and templates for request bodies.You must respect the package folder hierarchy. simulations: where to place your Simulations code.conf: configuration files for Gatling, Akka and Logback.bin: launch scripts for Gatling and the Recorder.If you get strange errors such as Unsupported major.minor version 51.0 and you were expecting to run a JDK8 or newer, you might want to explicitly set the JAVA_HOME env variable. Gatling launch scripts and Gatling maven plugin honor JAVA_HOME env var if it’s set.ĭepending on your setup, you might end up running a different version than the one displayed with java -version. Then, you’ll just need a text editor, possibly with Java or Scala syntactic coloration, to edit your simulations, and you’ll be able to launch Gatling from the command line.Ĭheck out our Open Source page for the download link. You can use Gatling as a standalone bundle. Those are not documented and released only for internal use or Gatling Enterprise customers. In particular, don’t use milestones (M versions) you could find on maven central, Make sure to use the latest version as documented on our website. Older Gatling versions only support Scala. Gatling 3.7 supports writing tests in Java, Kotlin and Scala.

Other JVMs such as JDK 12, client JVMs, 32bits systems or OpenJ9 are not supported. Gatling supports 64bits OpenJDK LTS (Long Term Support) versions: 8, 11 and 17. Learn about the Java, Kotlin and Scala requirements, install Gatling with the Bundle or build tool: maven, sbt, gradle Prerequisites # Java Version #

Launching Gatling and the Recorder from the IDE.

Install intellij on macbook pro