Test cases: Admin client events (UI telemetry)

Document control

Version	Date (UTC)	Summary
1.0.0	2026-05-13	Initial sheet from Client events (Admin)

---

Scope

• Route: /dashboard/client-events in admin-web.
• API: POST/DELETE …/auth/admin/ui-client-events/* (resolve, batch resolve, delete, batch delete).
• Storage: ui_client_events migration must be applied.

---

Scenario catalogue

List & filters

ID	Class	Scenario	Automation
TC-ACE-001	Happy	List loads with URL-synced filters (source, kind, severity, date range, errors-only)	E2E*
TC-ACE-002	Happy	Tabs All / Open / Resolved switch tab query; data refetches	E2E*
TC-ACE-003	Happy	Pagination matches other dashboard tables (reset on filter change)	E2E*
TC-ACE-004	Unhappy	Repository not wired (503) → clear error state in UI	Unit + E2E*

Detail & mutations

ID	Class	Scenario	Automation
TC-ACE-010	Happy	Open detail; stack / URL visible; no PII leak in export	E2E*
TC-ACE-011	Happy	Mark resolved on open event; list tab moves row to resolved	E2E*
TC-ACE-012	Happy	Delete single with confirm; returns to list	E2E*
TC-ACE-013	Unhappy	Resolve already resolved → stable API + UX	Unit

Batch (cap 200)

ID	Class	Scenario	Automation
TC-ACE-020	Happy	Select ≤200 rows; batch Mark resolved succeeds	E2E*
TC-ACE-021	Unhappy	Select >200 → toast / block per product rule (align with catalog batch)	E2E*
TC-ACE-022	Happy	Batch Delete with confirm	E2E*

Manual report

ID	Class	Scenario	Automation
TC-ACE-030	Happy	Report event form creates row for staging repro	E2E*
TC-ACE-031	Unhappy	Invalid payload on manual report → 400	Unit

Access

ID	Class	Scenario	Automation
TC-ACE-040	Unhappy	Non–System / non-master staff without route access → 403 or hidden nav	E2E*

---

Coverage checklist (this sheet)

• Indexes (resolved_at, etc.) verified under load
• Retention / purge policy documented in ops runbook when defined
• Payload redaction rules reviewed with security

Parent index: System test cases (index) · Admin web: Admin web