Test booking a slot on a meeting link

The contract this flow keeps

Four facts have to be right, and a booking missing any one of them generates an email to support rather than a meeting.

• Availability - four open times, so the page is offering something real.
• The selection - the chosen slot reflected back before any details are entered.
• The booking - a reference of MTG-20410 the prospect can quote.
• The participants - the host named and the prospect email echoed.

Echoing the email back is the assertion worth keeping. A meeting booked against a mistyped address sends the invitation nowhere, and the prospect sits waiting on a call that was never going to arrive.

The objective in plain English

The slot is asserted after the click and before the details are typed, which proves the selection registered rather than the page defaulting to the first available time.

---
mode: testing
url: https://my-testing-repo-main.vercel.app/hubspot-clone-app/meetings?reset=true
max_steps: 40
tags: [hubspot, crm, scheduling]
---

# Hubsprout 29.4: Meeting link booking

Catalog objective: book a slot on the meeting link as a prospect.
Key assertion: a meeting is created and a confirmation is shown.

## Verify the open slots
Verify the page title reads "Book time with Priya Nair" and "Times available" reads 4.

## Pick a slot
Click the time button "2026-09-18 14:30" and verify "Selected" reads "2026-09-18 14:30".

## Enter your details and book
Type "Sam Rivera" into "Name", "sam@riverfield.test" into "Email", and click "Confirm the meeting".

## Verify the confirmation
Verify a green card titled "You are booked in" shows "Reference" of "MTG-20410", "When" of "2026-09-18 14:30", "With" of "Priya Nair", "Your email" of "sam@riverfield.test" and a "Scheduled" badge.

The scheduled badge is asserted alongside the reference, since a booking recorded as pending is a different outcome from one that is confirmed.

Assertion by assertion

Availability, a selection, the details and the confirmation.

The time is asserted on both the selection and the confirmation, because a booking that drifts by an hour between the two is a timezone bug and those are rarely caught by hand.

Putting it in CI

kane-cli testmd run tests/hubspot/meeting-link-booking_test.md

Add a booking on an already taken slot, since double booking a host is the failure that costs the most credibility.

Scheduling involves timezones, which deserve explicit coverage. Generating the variants covers producing them, and the Kane CLI introduction covers getting started.