Airline Domain Overview (For Software Testers)
The airline domain involves managing flight booking, reservations, ticketing, check-in, boarding, payments, loyalty programs, and post-travel services. Airline systems are highly transactional, time-critical, and integration-heavy, making domain knowledge essential for testers.
Interviewers ask airline domain testing interview questions to evaluate whether a tester understands:
- End-to-end passenger journey
- Reservation and ticketing rules
- Pricing, fare rules, and cancellations
- Integration with airports, GDS, payment gateways, and loyalty systems
Why Airline Domain Knowledge Is Important
- Revenue directly depends on booking accuracy
- Seat inventory is real-time and limited
- Complex fare rules and rebooking logic
- Heavy integrations and high concurrency
- Customer experience is extremely sensitive
Typical Airline E2E Flow
- Flight search
- Fare selection
- Passenger details entry
- Seat selection & add-ons
- Payment & ticketing
- Booking confirmation (PNR)
- Check-in
- Boarding
- Flight completion
- Refunds / rebooking / loyalty updates
Major Modules in Airline Domain
| Module | Description | Key Testing Focus |
| Search & Availability | Flights & seat availability | Accuracy, performance |
| Reservations | Booking creation | PNR, data integrity |
| Fare Management | Pricing & fare rules | Correct fare breakup |
| Inventory | Seat management | Real-time sync |
| Payments | Ticket payment | Success/failure flows |
| Ticketing | E-ticket generation | Validity, uniqueness |
| Check-in | Online/airport check-in | Rules, eligibility |
| Boarding | Boarding passes | Status updates |
| Ancillaries | Meals, baggage, seats | Pricing & eligibility |
| Loyalty | Miles & rewards | Accrual & redemption |
| Operations | Flight status | Delays, cancellations |
Airline Domain Testing Interview Questions (Basic → Advanced)
Basic Airline Domain Interview Questions (1–15)
1. What is airline domain testing?
Testing airline applications to ensure booking, ticketing, check-in, and flight operations work correctly.
2. What is PNR?
Passenger Name Record – unique booking reference.
3. What is an e-ticket?
Electronic ticket issued after booking.
4. What is flight inventory?
Available seats on a flight.
5. What is fare?
Price of a ticket including base fare and taxes.
6. What is seat map?
Visual representation of seat availability.
7. What is check-in?
Passenger confirmation before boarding.
8. What is boarding pass?
Document allowing passenger to board aircraft.
9. What is GDS?
Global Distribution System (Amadeus, Sabre).
10. What is ancillary service?
Additional services like meals or baggage.
11. What is baggage allowance?
Free luggage limit per passenger.
12. What is cancellation?
Booking termination by passenger or airline.
13. What is refund?
Money returned after cancellation.
14. What is no-show?
Passenger does not board flight.
15. What is flight status?
On-time, delayed, cancelled.
Intermediate Airline Testing Interview Questions (16–40)
16. What types of fares exist?
Refundable, non-refundable, promotional.
17. What is dynamic pricing?
Fare changes based on demand and time.
18. What is overbooking?
Selling more tickets than seats.
19. What is rebooking?
Changing flight after booking.
20. What is itinerary?
Complete travel route.
21. What is code-share flight?
Flight operated by partner airline.
22. What is round-trip vs one-way?
| One-way | Round-trip |
| Single journey | Return journey |
23. What is SSR?
Special Service Request (wheelchair, meals).
24. What is standby passenger?
Passenger waiting for seat availability.
25. What is auto check-in?
System-initiated check-in.
26. What is fare breakup?
Base fare + taxes + fees.
27. What is ticket reissue?
Issuing new ticket after change.
28. What is loyalty program?
Miles earned for flights.
29. What is miles redemption?
Using miles to book flights.
30. What is disruption management?
Handling delays or cancellations.
Advanced Airline Domain Interview Questions (41–70)
41. How do you test flight search?
- Origin/destination
- Date & passenger count
- Multi-city flows
42. How do you test seat inventory?
- Real-time locking
- Concurrent bookings
43. How do you test fare calculation?
- Base fare
- Taxes
- Currency conversion
44. How do you test booking creation?
- PNR generation
- Data persistence
45. How do you test payment failures?
- Amount debited, booking failed
- Retry & refund logic
46. How do you test cancellation & refund?
- Fare rules applied
- Refund amount accuracy
47. How do you test check-in rules?
- Time window
- Passenger eligibility
48. How do you test overbooking scenarios?
- Seat assignment priority
- Compensation logic
49. How do you test loyalty points?
- Accrual after flight
- Redemption validation
50. How do you test flight delay handling?
- Notifications
- Rebooking options
Scenario-Based Airline Testing Questions (UAT / SIT)
Scenario 1: Payment Success but Ticket Not Issued
Validation:
- Payment callback
- PNR status
- Auto-refund trigger
Scenario 2: Seat Shown Available but Booking Fails
Checks:
- Inventory sync
- Cache vs DB mismatch
Scenario 3: Cancellation Charges Incorrect
Expected:
- Fare rule applied
- Correct refund amount
Scenario 4: Online Check-in Not Allowed
Validation:
- Check-in window
- Special service restrictions
Sample Airline Test Case Example
Test Case: Flight Booking with Seat Selection
| Field | Details |
| Precondition | Seats available |
| Steps | Search → Book → Pay |
| Expected | Ticket issued |
| Validation | UI + API + DB |
| Status | Pass |
BRD & FRD in Airline Projects
BRD (Business Requirement Document)
- Fare rules
- Cancellation policies
- Loyalty rules
FRD (Functional Requirement Document)
- Booking workflows
- API integrations
- Validation logic
Database + API + UI Validation in Airline Domain
UI Validation
- Fare shown
- Booking status
API Validation
- Booking & ticket APIs
- Payment callbacks
DB Validation
- PNR table
- Ticket table
- Seat inventory
Real-Time Production Defect Examples
- Seat double-booked due to concurrency issue
- Payment deducted but ticket not issued
- Incorrect refund calculation
- Loyalty points not credited
- Check-in allowed beyond cutoff time
High-Risk Areas in Airline Domain Testing
- Seat inventory & concurrency
- Pricing & fare rules
- Payments & refunds
- Check-in & boarding rules
- Third-party integrations
Test Design Approach for Airline Projects
- Requirement-based testing
- Risk-based testing
- Concurrency & load testing
- Negative & edge case testing
- End-to-end journey validation
Quick Revision Cheat Sheet
✔ Flight search → Booking → Ticket → Check-in → Boarding
✔ PNR & inventory
✔ Fare & refund rules
✔ Payment success/failure
✔ Loyalty & ancillaries
✔ UI + API + DB validation
FAQs – Airline Domain Testing Interview Questions
Q1. Is airline domain difficult for testers?
Not once booking and inventory flows are understood.
Q2. Are domain questions mandatory in airline interviews?
Yes, especially for reservation and ticketing systems.
Q3. Do testers need aviation knowledge?
Only functional and system-level understanding is required.