Booking and travel

Test booking journeys with AI agents.

Coming later: verify dates, availability, total price and policies. Agents stop before a booking starts.

Abstract booking journey connecting dates, time, availability, policy and a verified review boundary

For hotels, travel platforms, appointments, events and rentals.

Test the constraints that make a booking valid.

Scenarios combine dates, party size, inventory, fees, policy and locale instead of testing controls in isolation.

Search

Search by destination or service, dates and party size.

Interpret inventory

Distinguish sold out, unavailable and temporarily failed states.

Compare totals

Compare final price, fees, cancellation rules and timezone.

Select

Choose a valid room, rate, seat or appointment slot.

Stop before booking

Keep the selection up to the point where booking would start, then stop.

Recover

Handle an expired slot, session or inventory change without silent substitution.

Keep dates, inventory and policy attached to one choice.

The assertion chain prevents a plausible result from hiding a changed rate or slot.

  1. Valid search

    Destination, date format, timezone and party size are interpreted correctly.

  2. Comparable option

    Availability, total price and cancellation terms remain attached to the selected option.

  3. Stop point

    The chosen option is unchanged where booking would start, and the run stops there.

Booking failures often appear only after several correct steps.

Hidden fee

The result changes when fees appear late in the journey.

Timezone ambiguity

A slot looks valid but resolves to the wrong local time.

Inaccessible calendar

Custom date controls have no usable keyboard or accessibility-tree path.

Lost selection

Session expiry or a modal destroys dates, party size or chosen inventory.

A fast result must also be current and recoverable.

Timing is evaluated beside inventory accuracy, retries and final-state preservation.

Step screenshots

Follow search, comparison and the final check step by step, with masked screenshots.

Completion time

See how long search, results and each page step took.

Layout shifts

Measure layout shifts on calendars, rate cards and result pages.

State preservation

Assert that dates, guests, option and policy survive each transition.

Public runs stop before a real booking or payment.

AI agents stop before booking, payment or any form that sends data. Modification and cancellation tests with approved staging fixtures are coming later.

The audit covers dynamic inventory as well as page structure.

Signals are recorded for diagnosis even when they do not change the verdict.

  • Event, Hotel, LodgingBusiness and Offer structured data
  • Date, time, timezone and locale semantics
  • Calendar and modal accessibility
  • Inventory APIs, caching and session persistence
  • Network behavior and layout shifts during task runs
  • Declared WebMCP forms when present: detected, not run

The result explains where booking intent was lost.

  • Journey and inventory assertions
  • Step screenshots with step timings
  • Price, fee, policy and timezone discrepancies
  • Recovery findings with reproduction steps
  • Prioritized engineering backlog and retest baseline

Booking audit questions

Do public tests create real bookings?

No. The run stops before the final booking or payment action.

Can cancellation be tested?

Coming later, with an approved staging site and test bookings.

How are changing prices handled?

The run records timestamps, inputs and observed states so expected inventory movement is distinct from inconsistency.

Practical testing guide

Model booking state before running an agent.

Use the booking task, timezone, inventory, policy, expiry and stop-gate contracts to build a repeatable scenario.

Read the booking testing guide

Protect the path from search to booking review.

Apply with one high-value search, comparison or appointment workflow for a private review.