A failed booking is a customer who never tells you
Calendars and availability rules make bookings one of the most fragile flows on a site.
- Date pickers and time slots break in ways a quick manual check misses.
- A customer who can’t book goes elsewhere instead of reporting the bug.
- Clicking through dates, options and confirmations by hand doesn’t scale.
Check the whole booking, end to end, every day
Write the booking steps
Write the booking steps and what the confirmation should say. BuniOD matches each step to your pages and uses the test data you give it.
Check the confirmation email
With a test identity, the scenario can check the booking email that arrives in its own inbox.
Run it every day
Confirmed scenarios run once a day at a time you choose, or on demand.
See what broke
A failed run shows the step or check that failed, with a screenshot and console and network logs.
From written steps to a runnable test
Prompt: the steps you write
// Book a fitting 1. Click on "Book a fitting" in the header 2. Select "Tashkent" in the "Store" dropdown 3. Click on the first available Saturday slot before 12:00 4. Fill in the name and email from "Test Customer" 5. Click on "Confirm booking" and wait for 5 seconds 6. Confirm you see the text "Booking confirmed" // Clean up, so the slot is free again 7. Click on "Cancel booking", then on "Yes, cancel"
Expected result
A booking email is in the inbox of “Test Customer”, and the booking shows the status “Cancelled”.
Steps matched on the page
- Click “Book a fitting” in the header
- Choose “Tashkent” in the store dropdown
- Click the first free Saturday slot before 12:00
- Type the test identity’s name and email
- Click “Confirm booking” and wait 5 seconds
- Click “Cancel booking”, then “Yes, cancel”
Checks
- “Booking confirmed” is visible (step 6)
- A booking email arrives in the test inbox
- The booking shows the status “Cancelled”
Demo data: Acme Shop — Staging. Your scenario follows your own pages.
Three steps to a daily check
Connect your site
Add your staging URL. Public pages need nothing else; signed-in areas use HTTP basic auth or a test identity.
Write the steps
Write the test steps and the expected result in plain language, the way you would brief a tester. BuniOD matches each step to your page and adds the checks.
Review, then run daily
Confirm the scenario, run it on demand or once a day, and see the failed step with a screenshot and logs.
Free plan with 500K tokens a month · Pro $39/mo · Scale $59/mo · unlimited projects and scenarios on every plan.
See pricingQuestions
Won’t the test fill our calendar with fake bookings?
Scenarios act like a real user, so they do create bookings. Run them on a staging environment, and reset test data there as you need.
Can it handle a deposit or payment step?
Yes, on staging with your payment provider’s test mode and test card — never with a real card.
Does it check the booking email?
Yes, when the scenario uses a test identity: each one has its own inbox, so the scenario can check what your system sends.