Test seat selection and the price it produces

The flow under test

The interesting assertion is the price line, because it makes the relationship between seat count and seat price explicit rather than leaving the total unexplained.

• The movie and showtime - selected in sequence, each revealing the next step.
• The seats - B2 and B3, reflected back as a selection.
• The price line - two seats at 220 rupees, producing 440.
• The booking - naming the film, the showtime, the seats and the amount paid.

Asserting two times 220 alongside the total of 440 is what catches a price applied per booking rather than per seat. A single total assertion would pass a flow that charges for one seat and reserves two.

The test file

The booking confirmation is asserted with the showtime included, since a ticket for the right film at the wrong time is a complete failure that a film-only assertion would miss.

---
mode: testing
url: https://my-testing-repo-main.vercel.app/paytm-clone-app/movies?reset=true
max_steps: 45
tags: [paytm, fintech, booking]
---

# Paytem 20.5: Movie ticket

Catalog objective: book a movie seat and reach payment.
Key assertion: the seat is locked with the correct show and price.

## Pick the movie
Click the select button on "Kalkii 2898" and verify a "Showtimes · Kalkii 2898" card appears.

## Pick the showtime
Click "6:20 PM" and verify a "Choose your seats" seat map appears.

## Choose two seats
Click seat "B2" and seat "B3", then verify "Seats selected" reads "B2, B3" and the price line reads "2 × ₹220.00" with a total of "₹440.00".

## Reach payment
Click "Proceed to payment" and verify a green banner titled "Booking confirmed" names "Kalkii 2898" at "6:20 PM" with seats "B2, B3", and the ticket shows "Amount paid" of "₹440.00".

Each selection step asserts that the next stage appeared, which keeps a multi-stage booking flow attributable rather than failing at the end with no indication of where.

Step by step coverage

Three selections and a confirmation.

A staged flow where each step asserts the appearance of the next is the pattern to copy for any wizard. It turns one opaque failure into a specific one.

Running it

kane-cli testmd run tests/paytm/movie-ticket_test.md

Add a variant that attempts an already booked seat, since seat contention is the behaviour that actually distinguishes a booking system from a form.

Multi-stage flows are where a compound step most often stalls. Running interactively is the quickest way to iterate on one, and generating the variants covers the contention case.