Test the Buyer Journey

Do not stop at component checks. Test the full buyer journey:

1. landing page
2. checkout
3. /checkout/success
4. sign-in or post-payment account creation when needed
5. product-access claim and grant
6. /start
7. the first incomplete packet-first stage

The four realities

Every pass should cover these states:

• signed out
• signed in without access
• signed in with access
• newly paid and waiting for access grant

The fastest local flow

1. Follow Local QA.
2. Use the no-access QA account for locked-state checks.
3. Use the granted-access QA account for product checks.
4. Run a real local Stripe test checkout before you trust the handoff.

What to confirm

• signed-out users can start checkout directly from the primary CTA
• users without access land on /start and see inline recovery
• checkout returns to /checkout/success
• /checkout/success offers sign-in or account creation when payment happened before auth
• the webhook grants access
• the app recovers automatically into /start
• the first protected page does not throw a client-side Unauthorized error during hydration
• the next packet-first stage loads after access appears

What success looks like

You are ready for a production pass when the buyer journey works without fake shortcuts or manual database intervention.