24 lines
872 B
Markdown
24 lines
872 B
Markdown
# UI E2E Cases
|
|
|
|
Focused UI contract checks for the plugin calendar page and related user flows.
|
|
|
|
## Scope
|
|
- Calendar page controls render (`/calendar`)
|
|
- Account actions used by UI (register, login, reset)
|
|
- Event CRUD and single-occurrence delete semantics used by UI
|
|
- Admin user approval/removal flow that unblocks UI write access
|
|
|
|
## Automated Script
|
|
- `compatibility-layer/ui_e2e.sh`
|
|
|
|
## Cases
|
|
1. Calendar page renders login/event controls.
|
|
2. Calendar page renders verify/reset/future-only/theme and recurrence-delete controls.
|
|
3. Register user and verify email token flow.
|
|
4. Admin approves user.
|
|
5. Approved user login succeeds via `/users/me`.
|
|
6. User creates recurring event.
|
|
7. Single occurrence delete removes only selected occurrence.
|
|
8. User deletes event and resource becomes not found.
|
|
9. Admin removes user and `/users/me` authentication fails afterward.
|