Gatling Reviews & Product Details

Flexibility. I like to write in Scala, others prefer Kotlin, Frontend and QA colleagues prefer TypeScript or Javascript. All as code, all in cloud. Perfect setup for current times Review collected by and hosted on G2.com.

Setting up the internal network runners is not ideal, but nothing overcomplicated Review collected by and hosted on G2.com.

Gatling and the Gatling Enterprise API streamlines our load testing development and scheduling flow.

We were able to build a command line tool to automate the simulation scheduling flow so that our developers could iterate fast. Review collected by and hosted on G2.com.

I think more code examples, especially completed projects could be really helpful for users to understand the expected usage of certain features. Review collected by and hosted on G2.com.

If you are looking for a powerful and modern tool for performance testing, Gatling is one of the best options on the market. Its non-blocking architecture allows it to simulate thousands of users with efficient resource consumption, and its code-based approach facilitates integration with CI/CD pipelines. Additionally, it generates detailed, visual, and easy-to-interpret reports. Ideal for technical teams that need precision, speed, and automation in their load testing. Review collected by and hosted on G2.com.

What I would like to see in Gatling is a more united and active community, where sharing best practices, use cases, and support among users is more common. Additionally, I believe that more concise and structured documentation would help a lot, especially for those who are starting or want to integrate Gatling quickly into their pipelines. Even so, it is a very powerful and efficient tool for performance testing. Review collected by and hosted on G2.com.

One of the first tools I used for performance testing, and to this day, it's still the one I use the most to run large-scale tests. It's lightweight, captures flows easily with its recorder, and the logs are easy to understand—making Gatling, for me, the perfect tool for my analyses.

- Excellent (dynamic) reporting

- Support for different programming languages

- Easy-to-understand and learn documentation

- Open source with an easy-to-use injection platform

- Integration in CI/CD Review collected by and hosted on G2.com.

Although I don't have many remarks, I would like to see the integration with Grafana resumed and the addition of more open-source protocols for the community. Review collected by and hosted on G2.com.

I really like how Gatling has strengthened its integration with modern CI/CD pipelines, such as Jenkins, GitLab, and GitHub Actions. The ability to seamlessly automate performance tests within DevOps workflows ensures performance benchmarks are met before deployment, which is crucial for high-traffic events like product launches or Black Friday sales. This makes Gatling a go-to for teams aiming for continuous quality.

Review collected by and hosted on G2.com.

Learning Curve for Non-Developers: Gatling’s Scala-based DSL (Domain-Specific Language) is expressive but can be challenging for testers without programming experience. Improving the documentation with more beginner-friendly tutorials or introducing a GUI-based test recorder (like JMeter’s) could make it more accessible to non-coders, broadening its user base. Review collected by and hosted on G2.com.

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.