Coldstart Empty

Generated

This page is generated from qa/customer/specs/coldstart-empty.md — the source of truth. Edit the spec, not this page.

Last run: not yet recorded (run the replay suite to populate status).

Overview

The onboarding flow’s two cold-start empty states render cleanly, never as errors:

• org-has-no-domains — immediately after creating the org, the customer has zero workspaces; the surface presents the “create your first workspace” step rather than an empty/error screen.
• domain-has-no-published-world — when no operator has published a world yet, the first-workspace step shows the “no published world is available yet” empty state instead of a picker, and never an error toast.

Preconditions

• The stack is running in replay mode at the customer base URL.
• SUPABASE_ANON_KEY is resolvable (the org-less signup mints the onboarding user).

Scenarios

1. org-has-no-domains → the first-workspace step (not an error)

• Mint an org-less session, land on /auth/onboard, create the org
• Expected: The “Create your first workspace” step renders (a zero-workspace org is a valid resting state); no error state shows.

2. domain-has-no-published-world → world cold-start empty state

• On the first-workspace step, when no world is published, observe the surface
• Expected: The “no published world is available yet” empty state renders; no error toast. (Skipped when a world IS published — the empty state is conditional on the fixture.)

Test Data

Label	Value	Notes
Org-less user email	qa-orgless-@spectral.local	Minted fresh per run