Content Type QA - Event
Run common.md first. This file covers Event behavior for /content/event and /content/event/{id}.
Totals
| Priority |
Count |
| P0 |
4 |
| P1 |
3 |
| P2 |
2 |
| P3 |
1 |
| Total |
10 |
P0 - Release blockers
P0-01 - Event list and detail route load
| Field |
Value |
| Type |
Functional + API |
| Description |
Event list must load and navigate to details without failure. |
| Verify |
UI + DevTools Network. Confirm eventList succeeds. |
| Pass |
Rows render and open /content/event/{id} correctly. |
| Fail |
Query fails, rows malformed, or navigation fails. |
P0-02 - Event create persists record
| Field |
Value |
| Type |
Functional + API |
| Description |
Creating an event should persist a new event record. |
| Verify |
UI + DevTools Network. Confirm eventCreate succeeds. |
| Pass |
New event appears in list and opens in details. |
| Fail |
Create feedback is false-positive or mutation fails. |
P0-03 - Event detail save persists updates
| Field |
Value |
| Type |
Functional + API |
| Description |
Event metadata and linked values should persist through save. |
| Verify |
UI + DevTools Network. Confirm eventUpdate succeeds. |
| Pass |
Edited values persist after refresh. |
| Fail |
Updates revert or mutation errors occur. |
P0-04 - Schedule linkage remains valid
| Field |
Value |
| Type |
Functional |
| Description |
Schedule linkage from event details should remain editable and consistent. |
| Verify |
UI only in Schedule tab. |
| Pass |
Linked schedule values save and reload correctly. |
| Fail |
Linkage fails to save or displays inconsistent references. |
P1 - Core event flows
P1-01 - Players and broadcaster tabs are functional
| Field |
Value |
| Type |
Functional |
| Description |
Players and broadcaster data should be editable and persistent in event details. |
| Verify |
UI only in Players and Broadcaster tabs. |
| Pass |
Updates are retained after save and refresh. |
| Fail |
Tab actions fail or values are lost. |
P1-02 - Editor tab content persistence
| Field |
Value |
| Type |
Functional |
| Description |
Event editor content should save and reload without corruption. |
| Verify |
UI only in Editor tab. |
| Pass |
Content persists exactly as saved. |
| Fail |
Content is lost or malformed after save/refresh. |
P1-03 - List search and sort behavior
| Field |
Value |
| Type |
Functional + API |
| Description |
Event list filtering and sorting should align with user selections. |
| Verify |
UI + DevTools Network (eventList variables). |
| Pass |
Returned rows match selected filters/sort criteria. |
| Fail |
UI controls and returned result set diverge. |
P2 - Secondary event checks
P2-01 - Additional metadata tab stability
| Field |
Value |
| Type |
UI |
| Description |
Metadata and macros section should load consistently for events. |
| Verify |
UI only. |
| Pass |
Tab renders expected controls and remains stable while editing. |
| Fail |
Tab content is missing or causes runtime errors. |
P2-02 - Unsupported actions remain hidden
| Field |
Value |
| Type |
UI |
| Description |
Non-applicable actions for current event status/role should not be available. |
| Verify |
UI only on at least two status states. |
| Pass |
Only valid actions are visible. |
| Fail |
Disallowed actions are shown or executable. |
P3 - Polish
P3-01 - Event detail interactions are console-clean
| Field |
Value |
| Type |
UI + API |
| Description |
Normal event detail interactions should not produce uncaught console exceptions. |
| Verify |
UI + DevTools Console during tab edits and save. |
| Pass |
No uncaught runtime errors on happy path. |
| Fail |
Console shows uncaught errors tied to event interactions. |