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

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.

In my QA role, I relied heavily on Gatling to stress-test our core vehicle-booking flows. The standout feature for me was Gatling’s code-as-configuration DSL. Since we could write load tests as code, we kept them in version control right alongside the application code. That shift changed our workflow significantly and saved our QA team hours of manual test maintenance each week, especially compared with UI-heavy legacy tools. Another benefit I didn’t expect at first was how smoothly Gatling fit into our existing CI/CD pipelines. It didn’t just enable large, concurrent stress tests; it also gave us immediate, automated performance feedback on new deployments. On top of that, the out-of-the-box HTML reporting is excellent—it helped us quickly pinpoint specific database bottlenecks during high-traffic booking simulations without needing to set up external visualization dashboards.