States

Generated

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

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

Overview

Each customer dashboard read should communicate its loading, empty, and error states rather than rendering blank or broken. A customer whose domain has no decisions yet, or whose read is slow/failing, should see an intentional state.

Preconditions

• Signed in as the seeded QA customer.

Scenarios

1. Empty decisions feed

• Open the Decisions tab for a domain with no recorded decisions
• Expected: An explicit empty state rather than a blank feed.

2. Loading state on a slow read

• Open a dashboard tab while its read is still in flight
• Expected: A loading indicator is shown while the read loads.

3. Error state on a failed read

• Open a dashboard tab whose backend read fails
• Expected: An error message (role=alert) is shown rather than a blank or crashed surface.

4. Unconfigured world model surface

• Open Rules tab (/world-model) for a domain whose world is not yet deployed
• Expected: An explicit empty/unconfigured state rather than an error or blank.

Test Data

Label	Value	Notes
Empty-domain customer	(a seeded customer with no decisions)	Drives the empty states