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.

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

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.