
SunExpress
2,500 pages of analysis. 15,141 test cases.
Overview
SunExpress is a Türkiye-based airline founded in 1989 as a joint venture between Lufthansa and Turkish Airlines, flying to 92 destinations across 35 countries. Test design was carried out manually and coverage had not been standardised. In the work we carried out with AutoRunner, more than 2,500 pages of analysis documentation were converted into 15,141 test cases.
- Company
- SunExpress

- Founded
- 1989, a joint venture between Lufthansa and Turkish Airlines
- Network
- 92 destinations across 35 countries
- Industry
- Aviation
- Product used
- AutoRunner
Before and after
| Measure | Before | After |
|---|---|---|
| Test cases | Fragmented and incomplete coverage | 15,141 cases |
| Functional coverage | Not standardised | 90%+ within two weeks |
| Test design | Carried out manually | 70% less effort |
| Use of analysis documentation | Read, then converted by hand | Converted directly into test cases |
| Regression execution | Proceeding without control | Tied to a defined plan |
In aviation, coverage has to stay definable despite the volume of documentation
Aviation carries one of the heaviest documentation obligations of any industry. The requirements for booking, operations and passenger service systems are defined across thousands of pages of analysis documentation. That volume looks like an advantage, but in practice it works the other way: the larger the document, the lower the probability that all of it is ever converted into test cases.
Where coverage is derived by hand, the test suite represents not the whole document but the part the team found time to read. Coverage then becomes unmeasurable, and the question of what has not been tested goes unanswered at management level. In a regulated industry that is an audit problem, not only a quality one.
SunExpress needed to close the gap between the analysis documentation and the test suite: remove document volume as an obstacle and tie coverage to a figure that can be measured.

We converted analysis documents directly into test cases
Document analysis and test case generation
We worked through more than 2,500 pages of analysis documentation and converted it into test cases. By automating that conversion we removed document volume as an obstacle to coverage.

Coverage became measurable and design effort came down
More than 2,500 pages of analysis documentation were converted into 15,141 test cases. Which part of the document is covered by which case is now traceable.
Functional coverage rose above 90% within two weeks. Coverage now rests on measurement rather than estimation, and audit and internal reporting requests can be answered with a figure.
Test design effort fell by 70%. The capacity released was moved from writing test cases into coverage analysis and risk assessment.
