Gatling Pros and Cons

The customer support has been some of the best I have come across.

We required complex use cases for requests and gatling's DSL supported all the customizations we needed.

Being able to scale and test load test at massive traffic (the main reason we opted for gatling - we wanted to test at 1 million requests per second from multiple regions) has been amazing Review collected by and hosted on G2.com.

The public API for automating your scenarios rather limiting. i.e you can run simulations but not create them. Perhaps that has changed now

Although now it supports Java, when we started they only supported Scala. Review collected by and hosted on G2.com.

- Gatling is easy to use (even when you do not know Scala at all! I wrote tests on my first day)

- Good OOTB reporting

- Gatling Scala-based DSL allows to write complex scenarios, which are impossible with some other competitors (for example, unpack a protobuf response and assert its elements)

- Impressive performance based on async Akka toolkit

- Cloud managed solution is also available Review collected by and hosted on G2.com.

There is nothing I *dislike* about Gatling, I really have just one point here:

- Gatling is relatively new so community is smaller than of peers (if you have to write non-trivial solutions, you are likely to be the first to do it) Review collected by and hosted on G2.com.

# The flexibility with coding language

# Gatling academy is super useful

# JMS support is super useful which many open source testing tools lack

# Documentation is super clear and useful

# The integration options available are good Review collected by and hosted on G2.com.

Working with complex payload are tricky as it lacks some standard functions to modify the response.

Also apart from official documentation, issues in Java based Gatling is not easy to avail Review collected by and hosted on G2.com.

It is great that Gatling offers a free open source version as well as paid for enterprise options. What sets Gatling apart from other leading performance testing tools is that it is extremely flexible and versatile as you can pretty much develop any logic to support your Gatling tests. Gatling is also continuously improving and coming out with new features which makes the tool even more powerful. Review collected by and hosted on G2.com.

Some performance testers might not like Gatling because it is very dev oriented compared to other performance testing tools. It also doesn't support as many protocols as you'd get with HP's tooling. Review collected by and hosted on G2.com.

As an open-source performance testing tool, it excels at its intended purpose, particularly by efficiently invoking virtual users without impacting your local computer's resources. Review collected by and hosted on G2.com.

I invested a significant amount of time learning how to accomplish tasks with limited examples. Like any new tool, there was a learning curve involved. Initially, I focused on learning Gatling by studying the Scala DSL, which had a richer set of examples available. This helped me validate specific aspects against packaged software. Later, I transitioned to the Java DSL, which offered a smaller pool of examples for reference. Review collected by and hosted on G2.com.

It is a robust load-testing tool out in the market. It doesn't load your computer much when testing with 1000s of virtual users. Because of the scripting-based tool, it is easy to tweak and try out different options. It supports multi-languages - Scala, Java and Kotlin.

It also provides the ability to perform load testing for websocket based applications.

I love the beautiful reports. Review collected by and hosted on G2.com.

Because of no UI, there is a little of bit steep learning curve for non-programmers which could be frustrating. Documentation could be more precise like currently, for maven projects, documentation says for Java 8 use this dependency, but for Java 11 use another dependancy. I wasn't sure if it supports a higher version of Java because I had Java 19 installed and was getting some errors. I thought it could be due to an unsupported Java version.

Later got to know it supports all versions. Review collected by and hosted on G2.com.

The data points in the report are very easy to digest. Review collected by and hosted on G2.com.

Lack of updates in the tool that generates the files Review collected by and hosted on G2.com.

Lots of tools to express the testing scenario needed. You can automate many steps and have them graphed nicely in an understandable way at the end of the run. After parametrized, same scenario can be run ove multiple targets for comparison. Review collected by and hosted on G2.com.

Too steep learning curve, and very opinated about how to write the tests. Stuff needs to be idempotent or pure-functions, so some branch decisions are very hard to do. That until they removed some feature I used. Now it is impossible to do some decisions. Review collected by and hosted on G2.com.

I have used only Open Source version in few of my projects. I have used both Scala and Java versions. It's quite easy to set up, DSL is rreach.

Compared to GUI based tools here we have code - so one can apply all good coding practices and IDE support.

It can be easily integrated into your CI pipeline. Review collected by and hosted on G2.com.

Java version compared to Scala lacked some small features when it comes to some advanced usage.

One also has to get used to specific ways of dealing with immutable session objects which sometimes can be tricky. Review collected by and hosted on G2.com.

java/maven tool with posibilites integrating into current java projects (with a maven plugin help). Native integration with Github Actions. Gatling enteprise provides meaninful graphs & stats for A/B testing. Gatling Enterprise support is responsive and valuable. Review collected by and hosted on G2.com.

No native integrations with monitoring tools (DataDog. etc).

No test scehduler. Review collected by and hosted on G2.com.