Test a launch draw entry with two validation gates

The checks that matter

The draw has two validation gates and a confirmation state, and each of the three needs its own assertion.

Testing both refusals before the successful entry is what makes the successful entry meaningful. A draw that accepts entries from signed-out visitors or without a size produces a winner list nobody can fulfil.

The same flow as a test file

The gates are tested in the order a real entrant would hit them, signed out first and then signed in without a size, which is also the order that needs the least setup.

---
mode: testing
url: https://my-testing-repo-main.vercel.app/nike-clone-app/launch?reset=true
max_steps: 45
tags: [nike, launch, draw]
---

# Nyke 8.3: SNKRS draw entry

Catalog objective: enter a draw on a launch product.
Key assertion: the entry-confirmed state is shown.

## Confirm the launch product
Verify the launch page shows "Nyke Air Meridian 'First Light'" at "$210.00" with a badge reading "Draw closes September 20, 2026 at 9:00 AM".

## Confirm entry requires membership
Click "Enter draw" and verify an error appears reading "Sign in to your Nyke account to enter."

## Sign in
Click "Sign in", type "priya.nair@example.com" into Email, type "member2026" into Password, and click "Sign in", then verify a "Member" badge is shown.

## Confirm a size is required
Click "Enter draw" and verify an error appears reading "Choose the size you want."

## Enter the draw
Click "US 10", click "Enter draw", and verify the page shows "You're in the draw" with an entry id starting with "DRAW-", status "Entered - awaiting draw" and size "US 10".

The confirmation assertion checks three attributes together, the entry id prefix, the status and the size, because an entry recorded against the wrong size is worse than no entry at all. Run the test with:

kane-cli testmd run tests/nike/snkrs-draw_test.md

Run output

Five passes in 194 seconds. Sign-in was the slowest step at 56.9 seconds, since it fills two fields, submits and waits for a member badge to appear.

---
test: ../snkrs-draw_test.md
status: passed
started: 2026-09-15T10:44:50.503Z
duration_s: 194
session_id: 2b92806a-b9b7-4236-aa50-668a0ace9d6a
---

# Nyke 8.3: SNKRS draw entry - Result

## Confirm the launch product ✓ passed (31.6s)
md5: 10421be4cb72f40db7c91263cafb5416
Verify the launch page shows "Nyke Air Meridian 'First Light'" at "$210.00" with a badge reading "Draw closes September 20, 2026 at 9:00 AM".

## Confirm entry requires membership ✓ passed (24.6s)
md5: 4756331275e95168251127ce1c9a120a
Click "Enter draw" and verify an error appears reading "Sign in to your Nyke account to enter."

## Sign in ✓ passed (56.9s)
md5: e6f544252b45d7d087959558a149ac46
Click "Sign in", type "priya.nair@example.com" into Email, type "member2026" into Password, and click "Sign in", then verify a "Member" badge is shown.

## Confirm a size is required ✓ passed (27s)
md5: 2f03e608822041bb73baf51804315b7c
Click "Enter draw" and verify an error appears reading "Choose the size you want."

## Enter the draw ✓ passed (51.1s)
md5: f92f33fe82e2a3cedb9b7fa58208b656
Click "US 10", click "Enter draw", and verify the page shows "You're in the draw" with an entry id starting with "DRAW-", status "Entered - awaiting draw" and size "US 10".

The two gate checks together cost 51.6 seconds, about a quarter of the run, for the two assertions most likely to matter on the day. That is a good trade on a flow that only executes once.

Taking it further

What you have is a rehearsal for a flow that gets exactly one attempt, covering the refusals as carefully as the success.

Launch flows are also worth running from a pipeline on a schedule in the days before the drop. Kane CLI in CI covers scheduling, and Kane CLI as a QA agent covers where a one-shot flow fits alongside a regression suite.