How an airline implemented shift-left testing using Gatling Enterprise

The airline conducted performance testing at the end of the software development life cycle (SDLC). This practice made it challenging to implement software design changes, increased risk in performance testing, development delays, and unnecessary expenses.

Looking at this challenge as a value proposition, the airline developed a new framework to integrate performance testing in the early stages of the software development process. The new framework enabled developers to set up tests left in their CI/CD pipeline. With early testing, the developers could assess the performance of the feature and rectify it if needed. This means the poor-performing page will not reach the end customer or impact the airline's operations.

The airline deployed Gatling Enterprise to implement their new Agile Shift left model effectively. 

Distributed Testing, Real-time dashboards, and dedicated support from Gatling convinced the airline to begin component-level testing with Gatling Enterprise to implement their Agile Shift Level Model.

With Gatling Enterprise, the airline established a reliable performance testing framework for continuous testing in conjunction with Jenkins as a CI/CD early in the Software Development Life Cycle (SDLC).
Gatling Enterprise's load tests became a key component in their Agile Shift Level Model. The airline deployed Gatling Enterprise in EC2 instance and provided a web interface and APIs for proactive performance management to the airline.