Practice 03 · Boundary values

Planted bugs (6)

1. The number-of-tickets input has max="9" but the helper text says “Maximum 10 tickets per booking”. A user who reads the hint and enters 10 will get a browser validation error. The max attribute and the hint should agree.
2. The ticket input has value="0" and min="1". The default value is below the minimum, so the form starts in an invalid state. The default should be 1 (or empty, with required enforcing input).
3. The age input has min="0" but the helper text says “Must be 18 or over”. The min attribute should be 18 to match the stated requirement.
4. The promo code input has maxlength="8" but the placeholder shows “EARLYBIRD2025” (12 characters). The placeholder text exceeds the maxlength, so it can never be entered.
5. The special-requirements textarea has maxlength="500" but the placeholder says “Max 200 characters”. The maxlength and placeholder give conflicting limits.
6. The age input has max="120". While technically a valid human lifespan, this is overly permissive for an event booking form and offers no realistic upper bound. A more sensible max would be 100 or derived from a reasonable event attendee age range.

Boundary value testing: check that min, max, minlength, maxlength, and default values all match the stated requirements. Any mismatch between the HTML attribute and the visible hint is a bug.