Vidanta’s deals applied across its destinations and parks, from Nuevo Vallarta and Riviera Maya to the Jungala water park. Depending on the dates and length of a stay, a guest could unlock a different perk at checkout. We tested with three to six deals at a time, knowing the lineup would change as the business needed.

Checkout is where a booking either happens or doesn’t. If a deal applied to the wrong stay, guests would get perks they didn’t book, or miss ones they did. If the flow let someone double book, or failed at confirmation, the cost was a real reservation and a real guest.

We walked the full booking flow for each deal, from choosing a package to the confirmation, then tried to break it. All testing was manual and tracked in Jira.

Functional

Deals and packages across destinations and parks

Checkout

The full booking flow, through to confirmation

Error states

Every error in the flow, and what it told the guest

Double booking

The same stay couldn’t be booked twice

Accessibility

Screen reader and keyboard navigation

Visual

Builds compared against the designs

Regression & smoke

Existing booking flows still worked after each release

I was one of two or three QA analysts. Beyond testing, I flagged UX and UI issues in the error flows and on the deal landing page, leaving comments in Figma, and those notes shaped the final design.

1. 01Tested each deal and package through checkout to confirmation
2. 02Tested error states and double-booking protection
3. 03Gave UX and UI feedback on the error flows and the deal landing page