Test cases for train ticket booking and PNR status

1. Type the first few letters of the origin station and pick it from the suggestions.
2. Do the same for the destination, then tap swap once and swap back.
3. Pick a date and tap Search.

Expected: Suggestions show station names with codes, swap exchanges both fields, and results list each train's number, name, departure, arrival, duration and classes.

1. Open the date picker and try to tap yesterday's date.
2. Scroll to the last date the app allows and try the day after.
3. Pick tomorrow and return to the search form.

Expected: Past dates and dates beyond the booking window are disabled with a short note, today is marked by its IST date, and the form shows the picked date with its weekday.

1. From the results, open a train and choose a class and the general quota.
2. Check the availability shown for the next few dates.
3. Switch to another class and back.

Expected: Each date shows a clear status, such as available with a count, RAC or a waitlist number, along with the fare, and switching classes updates both.

1. Tap Book on an available date and add two adults with names, ages and genders.
2. Choose a lower berth preference for one and no preference for the other.
3. Open the review screen.

Expected: The review screen lists each passenger with age, gender and berth preference, and shows the train, class, quota, boarding station, date and total fare.

1. On the review screen, tap Pay and choose an installed UPI app.
2. Check the amount in the UPI app, then pay with the UPI PIN.
3. Return to the booking app.

Expected: The UPI app shows the same total as the review screen. The booking app then shows the ticket with a PNR and each passenger's coach and berth or waitlist number, followed by an SMS or email confirmation.

Why a real phone: Payment happens in a separate installed UPI app and returns to the booking app.

1. Open PNR status and enter the PNR of a test booking.
2. Pull to refresh the status screen.
3. Open the same booking from booking history and compare.

Expected: Both screens show the same status for each passenger, whether the chart is prepared, and when the status was last updated.

1. Open a confirmed test ticket with three passengers and tap Cancel.
2. Select only the second passenger and read the refund amount shown.
3. Confirm the cancellation and reopen the ticket.

Expected: The refund amount is shown before confirming, only the second passenger shows as cancelled, and the other two keep their coach and berth.

1. After cancelling, open the refund status from the booking or cancellation history.
2. Note the amount, reference number and where the refund will go.
3. Check the original payment method once the app shows the refund as complete.

Expected: The refund status shows the same amount as the cancellation screen with a reference and progress, and the original payment method receives that amount.

1. Before the tatkal window opens, save the passengers in the app's passenger list.
2. When the window opens, choose the tatkal quota and the class.
3. Add passengers from the saved list and complete payment.

Expected: Saved passengers fill in with one tap each, the fare breakdown shows any tatkal charges separately, and the ticket shows the tatkal quota with its status.

1. Pick the same station for From and To and tap Search.
2. Type a station name that does not exist and tap Search.

Expected: The app blocks both with a clear message, such as choose different stations or no station found, instead of an empty results page.

1. Choose the ladies quota on a train and class that offer it.
2. Add an adult male passenger and tap Continue.

Expected: The app blocks or warns using the quota rule it shows on screen, and the booking cannot reach payment with that passenger.

1. Choose the senior citizen quota and read the eligibility shown.
2. Add a passenger whose age is below that eligibility.
3. Tap Continue.

Expected: The app shows an inline message about the quota's eligibility and does not allow payment until the passenger or the quota is changed.

1. Enter a single-letter name, a name with digits and a name with initials and dots.
2. Enter an age of 0 for an adult, then 150.
3. Tap Continue after each entry.

Expected: Names with digits and impossible ages show inline errors, while names with initials such as R. K. Sharma are accepted or get a clear format hint.

1. In PNR status, enter 9 digits, then letters, then a 10-digit number not linked to a booking.
2. Tap Check after each.

Expected: Short or non-numeric entries are blocked before sending, and an unknown PNR shows a plain not-found message instead of a raw error or a blank screen.

1. Open a test ticket for a train that has already departed.
2. Look for the cancel option and tap it if shown.

Expected: The cancel option is hidden or explains why it is unavailable and what the user can do instead, without showing a refund amount.

1. Pick a train that starts in the evening and reaches your boarding station after midnight.
2. Search using the date you will actually board.
3. Book and read the date and time on the ticket.

Expected: The search on the boarding date finds the train, and the ticket shows the boarding date and time at your station, with any start date at the origin clearly labelled.

1. Search from a station partway along a train's route.
2. Book, then open the ticket and the boarding point details.
3. Change the boarding point if the app offers it.

Expected: The ticket shows the chosen boarding station with its own departure time, and a changed boarding point appears on the ticket and in PNR status.

1. Open a train with only a few berths left and start booking.
2. Book those berths from a second account on another phone.
3. Continue to payment on the first phone.

Expected: Before payment the first phone shows the new status, such as waitlist or RAC, with the fare, and asks the user to confirm or go back.

1. Book with a lower berth preference on a train with few lower berths left.
2. Open the ticket after booking.

Expected: The ticket clearly shows the berth actually allotted, separate from the preference. If an option to book only with the preferred berth was ticked, the booking does not go through with another berth.

1. Type the name of a large city with several stations into From.
2. Choose the all-stations option if offered, otherwise one station.
3. Search and check which station each train leaves from.

Expected: Suggestions list each station separately, and results label the departure station for every train so the user does not go to the wrong one.

1. Add a child passenger whose age is under the limit the app shows for children.
2. Choose with or without a berth, if the app offers it.
3. Open the review screen.

Expected: The review screen shows the child's berth choice and fare, and the total matches the sum of the per-passenger fares.

1. Tap Pay and open the UPI app as the booking countdown nears its end.
2. Wait in the UPI app until the countdown has run out, then pay.
3. Return to the booking app and open booking history.

Expected: The app shows either a confirmed ticket or a failed booking with refund status and a reference. It never shows a session-expired message alone with no word on the money.

Why a real phone: The timer runs out while a separate installed UPI app is in front.

1. Complete payment in the UPI app.
2. Turn on airplane mode before returning to the booking app.
3. Reconnect and check booking history and the bank account statement.

Expected: Booking history shows the booking as pending, booked or failed with a refund reference, never missing, and the app warns before letting the user pay again for the same journey.

Why a real phone: Needs a real UPI debit while the booking app loses its confirmation.

1. On a 3–4 GB RAM Xiaomi, Realme or Vivo phone, open several heavy apps.
2. Start payment and stay in the UPI app for a minute before paying.
3. Return through recent apps.

Expected: The booking app reopens on the booking status rather than a blank search screen, and shows the ticket or a pending state for that payment.

Why a real phone: OEM battery savers kill backgrounded apps on budget phones, unlike emulators.

1. Fill the search and passenger details a few minutes before the window opens.
2. Tap Book the moment the window opens, with other testers doing the same.
3. Retry when the app asks, without force-closing it.

Expected: The app shows a queue or busy message instead of crashing or logging out, keeps the filled details, and never charges twice for one booking.

1. On a train, bus or car journey, open PNR status where the signal keeps dropping.
2. Pull to refresh a few times as the network moves between 4G and 2G.

Expected: The app shows the last fetched status with its time, retries without an endless spinner, and says clearly when it is offline.

Why a real phone: Signal on the move switches towers and drops in ways emulators cannot copy.

1. Open a booked ticket once while online.
2. Turn on airplane mode and force-close the app.
3. Reopen the app and open the ticket from booking history.

Expected: The ticket opens offline with the PNR, train, date, coach, berth and passenger names, and shows when it was last updated.

1. Start adding passenger details and answer an incoming call.
2. Return to the app after a minute.
3. Continue to payment and take another call while in the UPI app.

Expected: Entered details are still there after the first call, and after the second the payment completes once with the ticket shown, or the app shows a clear pending state.

Why a real phone: Carrier calls take over the screen and pause apps differently on each OEM.

1. Start a booking so the session countdown appears.
2. Lock the screen for several minutes, then unlock.
3. Compare the countdown with the time that has really passed.

Expected: The countdown shows the true remaining time, or says the session has expired, instead of resuming from where it froze.

Why a real phone: Locked phones pause app timers differently, so countdowns can freeze on real devices.

1. Connect to a public Wi-Fi that shows a sign-in page, without signing in.
2. Open the app and search for trains.
3. Sign in to the Wi-Fi, or switch to mobile data, and retry.

Expected: The app says it cannot reach the internet instead of spinning, and works normally once the Wi-Fi sign-in is done or the phone moves to mobile data.

Why a real phone: Sign-in-page Wi-Fi and the phone's detection of it only happen on real networks.

1. Book a waitlisted test ticket on Xiaomi, Vivo or Oppo phones with default battery settings.
2. Swipe the app away from recent apps.
3. Wait for the status to change or the chart to be prepared.

Expected: A notification arrives with the new status for each passenger, and tapping it opens the ticket. Note any delay for each phone maker.

Why a real phone: Notification delivery after swipe-away depends on each OEM's battery and autostart settings.

1. On a phone with three UPI apps, tap Pay and look at the chooser.
2. Go back and pay by entering a UPI ID instead, if offered.
3. Approve the collect request in the UPI app before the countdown ends.

Expected: The chooser lists the installed UPI apps, and the UPI ID route sends a collect request that completes the booking once approved.

Why a real phone: The list of UPI apps comes from what is actually installed on the phone.

1. Tap the current location option on the From field, if the app offers it.
2. Allow location and wait for the station to fill.
3. Repeat with location denied.

Expected: With location allowed, the nearest station or a short list fills in. With it denied, the app falls back to typing without repeated prompts.

Why a real phone: Needs a real GPS fix, which is slow or unavailable indoors and inside stations.

1. Open the search, date picker and availability screens on a 5-inch Android phone.
2. Repeat on a small-screen iPhone.

Expected: The calendar fits without cut-off weekdays, class and quota tabs scroll, and the Book button stays visible above the system navigation bar.

1. As user A, book a ticket and save passengers, then log out.
2. Log in as user B on the same phone.
3. Open booking history, saved passengers and recent PNR searches.

Expected: User B sees none of user A's bookings, saved passengers, payment methods or recent PNRs.

1. Open a booked ticket and use Share, then Download if offered.
2. Open the shared text or file and read every field.

Expected: The shared ticket shows journey and passenger details but masks any ID number and payment details, and contains no link that opens the account without a login.

1. Switch the keyboard to Hindi and type a station name in Devanagari.
2. Type common Hinglish or older English spellings of a city name.
3. Switch the app language to Hindi and open the results.

Expected: Each search finds the right station, and with the app in Hindi, station names, statuses and buttons appear in Hindi without clipped text.

1. Turn on TalkBack or VoiceOver and search for trains.
2. Move through the date picker, class tabs and availability for each date.
3. Add a passenger and reach the review screen.

Expected: Every control announces a clear label, dates are read with day and month, and statuses are read in full, such as waitlist 12, not just WL12.

1. Set font size and display size to the maximum.
2. Open the results, availability and fare summary screens.

Expected: Train names, times, statuses and fares are not cut off or overlapping, and the Book and Pay buttons stay reachable.

1. Set the phone to a time zone outside India.
2. Open search results, a booked ticket and PNR status.
3. Start a booking for four passengers and read the fare breakdown.

Expected: Departure and arrival times stay in IST on every screen, and fares show in rupees with Indian grouping, such as ₹12,450, matching the amount charged.