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’s biggest strength, in my experience, is the developer experience when building test scripts. A lot of effort has clearly gone into the fluent style of writing tests, and even though the scenarios are written as code, they remain easy for humans to read and understand. Review collected by and hosted on G2.com.

There’s a lack of automatic correlation detection for test scripts, which makes the process more manual than it needs to be. Review collected by and hosted on G2.com.

I use Gatling for testing in both my previous and current company, and I really like their support. The switch from using Scala to TypeScript for writing tests has been a positive experience for me. The DSL (domain-specific language) that Gatling has is very intuitive, making it easy to use. I appreciate that it's easy to use, especially compared to tools like JMeter, and I like that you have something more tangible in the code form. The fact that developers can easily jump in and manage changes since it's code-based is great. I find the syntax clear, and the reporting feature is very user-friendly, providing a history of load tests that is quite helpful. The support for languages and clear syntax makes writing tests easier, even for people who might have never coded before. I also find the reporting crucial for quickly getting the information I need and spotting bottlenecks or slow requests at a glance. The feature that allows comparisons between different runs is something I appreciate very much. Additionally, the community support is great. I also recommended Gatling at my current company because I liked it. Setup is now easier thanks to moving from Scala to Java and TypeScript support, which I think helps in facilitating the setup. There's also a recording tool that can get you started quickly. I really like Gatling, think it's a great tool, and appreciate the great support from the community. Review collected by and hosted on G2.com.

I think maybe their documentation could be a bit more. It is good, but I think it could be improved. Sometimes, you get confusing information that might not be suitable for your case. I think that could be improved. Before, in my previous company, when I used their reporting, I had some bugs in terms of a layout break. If I have a long endpoint written, then the layout would break and basically make the report not useful to me. So I have to make workarounds there. 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.

I use Gatling for performance testing and I really like its functionality and reports. It's been good for all aspects so far. The initial setup was easy too, which was a plus. Review collected by and hosted on G2.com.

Nothing 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.