QA Tester Career in the Travel Industry

# booking_flow_test_cases.yaml — a real manual test suite for a travel app
# Structured test cases a QA tester would write and execute.

feature: Flight booking flow
priority: P0
owner: QA

scenarios:
  - id: TC-001
    title: Search returns results for a valid route
    given: "a valid origin DEL, destination BOM, date +7 days"
    when: "the user submits search"
    then:
      - "results are displayed within 3 seconds"
      - "each result shows airline, time, duration, price"
      - "prices match the expected currency (INR)"
    severity: critical

  - id: TC-002
    title: Selecting a fare shows correct breakdown
    given: "a selected flight with fare ₹5,500"
    when: "the user proceeds to review"
    then:
      - "base fare + taxes + fees = total shown"
      - "no hidden convenience fee appears at payment"
    severity: critical

  - id: TC-003
    title: Payment fails and booking is not created
    given: "a failing payment gateway"
    when: "the user attempts to pay"
    then:
      - "user sees a clear error message"
      - "no booking is created in the system"
      - "no amount is debited"
    severity: critical

  - id: TC-004
    title: Successful booking triggers confirmation
    given: "a valid payment method"
    when: "the user completes payment"
    then:
      - "booking confirmation is shown"
      - "email and SMS confirmations are sent"
      - "PNR is generated and persisted"
    severity: critical

# Why this reflects travel QA specifically:
# - The booking flow is the highest-risk surface in the product.
# - Every step is a business promise, not just a UI screen.
# - Payment failure paths matter as much as success paths.
# - Confirmation and PNR correctness is where trust is built.

# test_travel_pricing.py — API test for travel pricing
# Fast, targeted tests that catch the bugs most likely to reach production.

import requests

BASE_URL = "https://api.example-travel.com"


def test_search_returns_correct_currency():
    response = requests.post(
        f"{BASE_URL}/search",
        json={
            "origin": "DEL",
            "destination": "BOM",
            "date": "2026-12-15",
            "currency": "INR",
        },
    )
    assert response.status_code == 200
    data = response.json()
    assert data["currency"] == "INR"
    for flight in data["results"]:
        assert flight["price"]["currency"] == "INR"
        assert flight["price"]["amount"] > 0


def test_total_equals_base_plus_taxes_and_fees():
    response = requests.post(
        f"{BASE_URL}/fare/breakdown",
        json={"flight_id": "FL-123", "pax": 1},
    )
    assert response.status_code == 200
    data = response.json()
    base = data["base_fare"]
    taxes = data["taxes"]
    fees = data["fees"]
    total = data["total"]
    assert round(base + taxes + fees, 2) == round(total, 2)


def test_refund_is_calculated_per_airline_policy():
    response = requests.post(
        f"{BASE_URL}/booking/cancel",
        json={"pnr": "ABC123", "reason": "user_cancelled"},
    )
    assert response.status_code == 200
    data = response.json()
    assert data["refund"]["amount"] > 0
    assert data["refund"]["currency"] == "INR"
    assert data["refund"]["status"] in {"initiated", "processed"}


# Why this reflects travel QA specifically:
# - Currency correctness is a classic travel bug surface.
# - Price breakdown errors cause refund disputes.
# - Refund logic depends on airline policy — a business rule,
#   not just a technical one.

# test_booking_flow.py — a Playwright automation for a critical travel flow
# Books one flight end-to-end, with assertions at each step.

import re
from playwright.sync_api import sync_playwright, expect


def test_search_book_and_confirm():
    with sync_playwright() as p:
        browser = p.chromium.launch()
        page = browser.new_page()
        page.goto("https://example-travel.com")

        # Search
        page.fill('input[name="origin"]', "DEL")
        page.fill('input[name="destination"]', "BOM")
        page.click('button[type="submit"]')
        expect(page.locator(".flight-results")).to_be_visible(timeout=5000)

        # Select the first result
        page.locator(".flight-results .result").first.click()
        expect(page.locator(".fare-breakdown")).to_be_visible()

        # Proceed to payment
        page.click('button:has-text("Proceed to payment")')
        page.fill('input[name="card"]', "4111 1111 1111 1111")
        page.fill('input[name="expiry"]', "12/30")
        page.fill('input[name="cvv"]', "123")
        page.click('button:has-text("Pay")')

        # Confirmation
        expect(page).to_have_url(re.compile(r"/confirmation"))
        pnr = page.locator(".pnr").inner_text()
        assert pnr is not None and len(pnr) > 0

        browser.close()


# Why this reflects travel QA specifically:
# - The end-to-end flow is what actually earns revenue.
# - Every step is a real business assertion, not a UI check.
# - Automation keeps this flow tested on every release.
# - A flaky test here is a real bug signal, not noise.