Aviation · QA automation
Major airline
QA automation across the airline's customer-facing booking and loyalty platforms, plus the internal crew-scheduling suite.
The challenge
Every release carried a manual regression pack that took the better part of two weeks. Coverage was uneven, test cases were written from memory rather than from requirements, and defects that reached production were rarely traceable to a missing test.
What we did
Business experts mapped the release process before anything was automated, cutting the regression pack down to what the business actually needed proven. Engineers configured the packaged QA solution to draft, execute and triage tests against the airline's own requirements and defect history. Every generated test is checked against the stated acceptance criteria before it enters the pack.
Systems connected
- Requirements management
- Source control and CI
- Test management
- Defect tracking
- Staging environments
Timeline
- Weeks 1-2Release process reviewed, regression pack rationalized, baseline captured.
- Weeks 3-7Joint build against two product lines with the airline's engineers embedded.
- Weeks 8-11Run in parallel with the manual pack until the numbers agreed.
- Week 12Manual pack retired for covered areas. Method handed to the QA leads.
Start with one workflow.
Tell us the function that costs you the most and the number you already track for it. We will tell you whether it is a candidate, and what a quarter would look like.
contact@deepcertainty.com · Hoboken, NJ