The ability to add scenarios, the ability to configure concurrent users per second, and the ability to define how long a particular test should last are valuable features. After that, I can draw conclusive reports and graphs around how well the particular test took, how many API calls were successful versus how many errored out, how many were failing due to authentication errors, and what sort of granular errors I got. That really helps us understand the scale at which our system is performing. I rely on the fact that we are able to add a particular number of users per second as simulations in the code or in Gatling Enterprise. The reason it is very important for my team is because it mimics the way actual users use our product in their day-to-day lives where there are periods wherein our system and product receive way more traffic, and that traffic results in way more downstream traffic, which Gatling Enterprise perfectly helps me capture. It has led us to have really robust scalability testing, performance testing, and load testing, thereby making sure of our system integrity during crunch time or during times of peak traffic. It has helped build confidence in our systems. We saw fewer outages and fewer periods of slowness in the product. Our number of customer complaints or customer escalations reduced by almost 20 to 30 percent over the period of a year when we initially started using Gatling Enterprise. As more and more teams are adopting this, the number is growing. It has led to real positive impact here.
