Travel App Testing Checklist (Booking, Itinerary, Payment — 2026)

Travel apps handle money, dates, locations, partner-system integrations, and high-stress users in airports. A broken booking flow is lost revenue; a broken boarding pass screen is a missed flight. Thi

Travel apps handle money, dates, locations, partner-system integrations, and high-stress users in airports. A broken booking flow is lost revenue; a broken boarding pass screen is a missed flight. This checklist is what I walk through for any travel app before release.

Search and discovery

1. Origin / destination autocomplete returns airports, cities, train stations
2. Date picker respects min (today), max (365 days out usually)
3. Return date auto-adjusts when outbound changes
4. Passenger count selector (adults, children, infants) enforces per-carrier rules
5. Class / cabin selection available
6. Flexible dates / calendar view works
7. Multi-city search works

Results

1. Loading state visible for network-bound search
2. Results render within 3 seconds
3. Sort options (price, duration, departure time) functional
4. Filters (airlines, stops, times, bags, amenities) respected
5. Price shown with fees / taxes disclosed
6. "X seats left" urgency indicator accurate (not always "2 left")
7. Baggage policy linked / visible

Booking flow

1. Traveller details form pre-fills from profile
2. Passport fields validate by country
3. Frequent flyer / loyalty number validates format
4. Contact email / phone captured and validated
5. Seat selection (if offered) works — map loads, available seats tappable
6. Add-ons (bags, meals, insurance) clearly priced, checkable
7. Total clearly summed before payment
8. T&Cs checkbox functional (required before submit)

Payment

1. Saved payment methods usable
2. Card number input masks mid-entry
3. 3D Secure / OTP flow completes
4. Apple Pay / Google Pay where applicable
5. Currency conversion disclosed
6. Error on decline clear, retry possible
7. Booking ref issued immediately on success
8. Email confirmation within 60 seconds

Itinerary

1. Trip appears in "My Trips" immediately
2. Trip visible offline (cached)
3. Boarding pass generated 24h before departure (check-in window)
4. PDF boarding pass downloadable
5. Wallet integration (Apple Wallet, Google Wallet) works
6. Gate / time updates push-notified
7. Delay / cancel notifications actionable (rebook link)

Changes and cancellations

1. Change flow respects fare class rules (some are non-changeable)
2. Change fees disclosed before confirmation
3. Cancel flow respects cancellation window
4. Refund amount estimated accurately
5. Refund timeline disclosed (X-Y days)

Passport / identity

1. Passport scan (OCR) works on valid passports
2. Manual entry fallback if scan fails
3. Passport expiration warning (must be valid X months after travel)
4. Visa requirement flagged for destination

Maps / navigation

1. Airport maps load when selected
2. Directions from gate A to gate B correct
3. Hotel location accurate (map pin)

Notifications

1. Price drop alerts (if user opted in)
2. Gate change alerts
3. Check-in reminder 24h before
4. Delay alerts real-time

Accessibility

1. Form fields labeled for screen reader
2. Boarding pass barcode high-contrast for scanners
3. Colorblind-safe status (delayed / on-time / cancelled)
4. Large-text mode accommodates itinerary
5. Voice input for search

Multi-partner integration

1. Airline / hotel / car rental inventory synced
2. Partner downtime handled gracefully
3. Booking reference maps to partner systems

Edge cases

1. Midnight booking — date math correct across timezones
2. DST transition during trip — times displayed correctly
3. International data off — cached itinerary visible
4. App killed mid-booking — draft preserved
5. Two bookings in flight simultaneously — no cross-pollution
6. User loses passport mid-trip — support flow reachable

How SUSA tests travel apps

Personas:

• impatient — stresses search and checkout speed
• business_professional — tests efficiency of common flows (rebook, change)
• elderly — boarding pass readability, touch target sizes
• adversarial — attempts invalid dates, expired cards, edge inputs

Network intelligence captures partner API calls; flags slow flight-search endpoints that degrade UX.

susatest-agent test travel.apk --persona impatient --steps 200

Common bugs

• Duplicate charge on payment retry
• Return date before outbound (validation missing)
• Boarding pass barcode unreadable at gate (low contrast on bright phone)
• Push notifications fire for wrong flight (user ID mix-up)
• Partner downtime shows "try again" instead of alternative

Travel is one of the highest-stress UX surfaces. Run SUSA every release; pair with manual test on actual travel days when edge cases matter most.