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

In a nutshell, Gatling 3.1.1 & Gatling Enterprise 1.7.0 are out, and a fantastic announcement at the end of this post!

Gatling 3.1.1

We are very delighted to announce that we have just released Gatling 3.1.1.

You can find the full release note on GitHub. Here are the most noticeable changes and fixes:

  • #3631 fix checks on arrays
  • #3669 WebSocket events were not correctly logged
  • #3674 Uncached RawFileBodies floods the filesystem with temp files
  • #3671 It’s now possible to pass a custom keystore per virtual user
  • #3696 By default, Gatling feeders now automatically decide to use eager or batch loading strategy depending on file size
  • #3699 TLSv1.3 is now enabled by default
  • #3708 Gatling Expression Language now supports sequence syntax on tuples

Please note that the 3.1.0 charts module is broken. Also, Gatling 3.1 is source-compatible with Gatling 3.0 but not binary-compatible, meaning that compiled binaries must be recompiled.

Gatling Enterprise 1.7.0

We are thrilled to announce new exciting features for Gatling Enterprise! Here are our Top 3 brand new features!

1. Official support for Kubernetes and OpenShift

Gatling Enterprise already supports on-premises instances and most of the cloud providers of the market (Amazon Web Services, Google Cloud, Microsoft Azure, OpenStack, Digital Ocean). We made it really easy to run your tests, especially with a cluster of load injectors.

Gatling Enterprise now has official support for Kubernetes and OpenShift to deploy your load injectors.

“Pools” are preconfigured groups of load injectors that you can use to run your tests

2. Runs comparison

Gatling FrontLine already provided you with trends, which are graphs based on all your runs, with basic KPIs (response times distribution, requests, and responses, throughput). But you couldn’t customize them or extract the raw data.

You can now have a table comparing 2 runs of your choice. You can, for instance, compare your latest run with a baseline run.

You can now compare the metrics of 2 different runs to track your performance regressions form one run to another

3. Customizable PDF export

Gatling Enterprise included public links to share your dashboards with people who don’t have credentials to access your Gatling FrontLine instance.

But now, you can customize your reports and export them in PDF format. Add titles, text areas, comments, charts, run’s status, etc., and send them to whomever you like!

Screenshot of a customizable report in PDF format for a Gatling Enterprise (formerly Frontline) test

You can find the full release note of Gatling Enterprise 1.7.0 alongside the rest of the documentation here.

Brace yourselves: Gatling’s new design is coming!

Other exciting news: We are about to reveal our new identity. Gatling is growing increasingly each year and offers new products and services. Many things have changed in the past few years and even in the past few months.

We are at a turning point in our development, and we decided to rethink our identity to match our thrive for innovation.

Stay tuned! You can already see our new logo in the last releases! Our new website will be released in the following days.

If you attend the Devoxx fair in Paris, we will reveal our new design there, so feel free to come and say hi!

We are looking forward to getting your feedback on the last releases and our new identity!

The Gatling team

Related resources

You might also be interested in…