The client is a European airline with 5 development teams of approximately 6 members each.
They release software updates every 2 weeks to 1 month.
The client had a set of automated tests in Java, running on a complex and outdated legacy tool installed by an external vendor. Many accompanying modules were unused.
The automated tests were not integrated into the development pipeline.
Production deployments to fix defects were frequent. Proper validation was time-consuming due to required regression testing.
Key functional areas like API services and the mobile application were not covered by automated tests, leading to additional manual testing during every release.
After a risk analysis, we prioritized automation efforts, starting with the web application and migrating the existing tests to a modern, open-source framework.
In parallel, we initiated:
All tests were configured to execute automatically upon repository changes, scheduled nightly, or triggered manually as needed.
Within two months, the new framework replaced the old one, reducing execution time by 80% and expanding coverage with critical tests.
By the third month, 100% of critical mobile tests were covered, and by the fourth month, 100% of service tests were included.
All tests are now integrated into the development pipeline, generating result reports after each execution.
The value delivery frequency increased due to reduced regression testing time, and the number of defects reported by end-users decreased significantly.
After 2 months with a new framework.
Adding mobile tests and service tests.