Attention, this article is about an outdated version of Gatling.
Please check-out the following links to access the information about the last version of Gatling:

→ current Gatling Open-Source version
→ current Gatling Enterprise version
→ current Milestones

We are thrilled to announce that we just released the first release candidate of Gatling 3! 4 years after the release of Gatling 2, all the Gatling team is really proud to present you this new major version of Gatling! We need you to use and test it as much as you can before we release the stable version. But first, let’s have a look at what Gatling 3 includes!

Why Gatling 3

We’re bringing new exciting features and major internals refactoring, such as:

Java 9+ support required changing the way we compile Scala code in the gatling-maven-plugin and the standalone bundle.
We parted ways with AsyncHttpClient. Gatling now has its own internal HTTP client, still implemented on top of Netty, that supports HTTP/2 and solves the concurrent access complexity issues AsyncHttpClient has.
The WebSocket support was completely re-implemented and re-designed as the previous one was brittle and lacking feedback from our users.
Gatling has now built-in support for closed workload model: you no longer have to make your virtual users loop and reset them.
Batching feeders you can use to not load the full data in memory

All in all, lots of Gatling internals have changed, so it was natural to go with a new major release.
A major release was also the chance to fix some annoying consistency issues in the Gatling DSL, such as some injection profiles using during while others are using over, or some keywords not using proper camel case names, eg baseURL.

All those new features will be detailed in upcoming posts.

Migrating

For most users, migration should be pretty straightforward: mostly renaming methods and fixing feeder paths.
The exception is WebSocket users as Gatling WebSocket support is completely different.

Make sure to read the migration guide for how to adapt your existing code, and the what’s new page for how to make the best use of the new features.

Release Candidates: We Need You!

We plan on having one release candidate per week during one month.

We’ve released Gatling 3.0.0-RC1 last Monday.

If Gatling matters to you and your organization, now’s your last chance to check the changes, raise your opinion and provide feedback. Once the stable release is out, it will be too late and Gatling DSL and behavior won’t change for a long time.