Gatling Enterprise Cloud

What do you like best about the product?

I love Gatling for its excellent tool features, including great language compatibility, especially with Scala. It's very robust, easy to maintain, and highly scalable. Gatling is a must for beginners because it's effortless to manage code and easy to begin with. I like its multi-language compatibility and the reports generated by Gatling are true gems, providing an entire snapshot of performance tests at a glance. The official documentation is great for setup, which makes it easy to use.

What do you dislike about the product?

I feel that many professionals don't even know about it, and I think the marketing can be improved.

What problems is the product solving and how is that benefiting you?

I find Gatling offers effortless code management and multi-language compatibility, and it generates detailed reports for performance testing. It's robust, scalable, and easy for me as a beginner.

What do you like best about the product?

It would be great to allow scripting in a couple of programming languages, e.g., Kotlin and Scala.

What do you dislike about the product?

There’s a lack of documentation for integrating with custom logging tools, such as Grafana or Sumo Logic.

What problems is the product solving and how is that benefiting you?

Performance testing.

What do you like best about the product?

Its Async and non blocking architecture make it possible to simulate thousands of concurrent users effectively also reporting capabilities

What do you dislike about the product?

Some Advance features may require additional time to understand and configure the framework

What problems is the product solving and how is that benefiting you?

I use Gatling for performance and load testing. It efficiently simulates thousands of users with minimal resources, offers excellent, detailed reports, supports concurrency, and is developer-friendly with easy CI/CD integration.

What do you like best about the product?

Gatling is an easy-to-use tool with a user-friendly UI.

What do you dislike about the product?

So far, I haven’t noticed any negative points.

What problems is the product solving and how is that benefiting you?

I use it for load testing with various protocols.

What do you like best about the product?

The best thing I like is that it supports performance testing and load testing as code, making it very easy to write in Scala. Gatling can be configured as code, which I prefer over JMeter's XML configuration. The initial setup was pretty easy because Gatling works via simple coding scripts. The best part is that it is developer-friendly, which is why it is gaining popularity.

What do you dislike about the product?

Sometimes it's difficult for me to simulate the exact number of users or to actually have a understanding about count of how the ramp-up of the users is working. If it is more readable or maybe there is better documentation for that, it would help us to understand the number of users.

What problems is the product solving and how is that benefiting you?

I use Gatling to identify performance issues and memory leaks, enabling fine-tuning of my application. It's great for performance and load testing as code in Scala, which makes it easy to write and customize. The Gatling charts are also offers quite meaningful information.

What do you like best about the product?

I’ve used multiple tools like JMeter, LR, and NeoLoad, and compared to them, this one feels lightweight. It helps us execute higher loads while using fewer resources.

What do you dislike about the product?

It needs to improve in terms of protocol support. Market leaders like Jmeter, NL, and LR offer a much wider variety of supported protocols, which Gatling currently doesn’t have.

What problems is the product solving and how is that benefiting you?

We needed to run a large load test with limited resources, and with JMeter we were feeling constrained. That’s where Gatling helped us. Now, with it available, we can quickly create Scala scripts and execute them.

What do you like best about the product?

Gatling’s code-based approach makes it easy to create, maintain, and integrate performance tests into CI/CD pipelines.

What do you dislike about the product?

The initial learning curve can be a bit steep, especially for teams new to code-based performance testing.

What problems is the product solving and how is that benefiting you?

Gatling helps us automate performance and load testing, identify bottlenecks early, and integrate performance checks into CI/CD, improving release confidence and reducing production performance risks.

What do you like best about the product?

I like Gatling because it is easy to use for performance testing and has a clean interface. It helps me create and run load tests without too much complexity. The reports are also easy to understand, which makes it simple for beginners to identify performance issues and check how the application behaves under load.

What do you dislike about the product?

The main thing I dislike about Gatling is that it can take some time for beginners to understand the setup and scripting. Some features require learning the Gatling syntax, and the documentation can feel a little overwhelming at first. It would be easier if there were more beginner-friendly examples and a simpler setup process.

What problems is the product solving and how is that benefiting you?

Gatling helps us identify performance and load-related issues before they affect users. It allows us to test how our application performs under different levels of traffic and find slow or unstable areas. This helps us improve application performance, reduce production issues, and feel more confident before releases.

What do you like best about the product?

I like that it’s possible to write tests via script/tests instead of relying on the GUI, as competitors tend to do.
The report output

What do you dislike about the product?

At the beginning, the only supported language was Scala; now Java, Kotlin, TypeScript, and JavaScript are supported as well.

What problems is the product solving and how is that benefiting you?

It’s very easy to store tests in a repository and keep them versioned, which is super useful on big projects.
And with the mvn/gradle task is easy integrate it in perf/load test stage in a pipeline

What do you like best about the product?

I really enjoyed using Gatling for my web/mobile project with an aggressive deadline. It did a fantastic job, letting us simulate thousands of users with ease and without heavy ram or CPU load, which created a quick feedback loop. The excellent recorder tool made it straightforward for load testing, and as an automation tester, I appreciated being able to use JavaScript without needing to learn additional languages. Also, I like the record and playback tool and the fact that I could present the results of testing back to stakeholders quickly.

What do you dislike about the product?

I found the learning curve challenging due to the project's tight timeline. I would benefit from courses that accommodate different learning styles since I'm a visual learner.

What problems is the product solving and how is that benefiting you?

Gatling allowed us to simulate thousands of users, providing a quick feedback loop without heavy resource use. Its recorder tool made the process straightforward, and I could use JavaScript, saving time. Presenting results to stakeholders was quick, despite the initial learning curve.