#@ Content Type QA - League
Run common.md first. This file covers League behavior for /content/league and /content/league/{id}.
Totals
| Priority |
Count |
| P0 |
4 |
| P1 |
2 |
| P2 |
2 |
| P3 |
1 |
| Total |
9 |
P0 - Release blockers
P0-01 - League list and details load
| Field |
Value |
| Type |
Functional + API |
| Description |
League list should load and navigate to details correctly. |
| Verify |
UI + DevTools Network. Confirm leagueList succeeds. |
| Pass |
Rows render and open /content/league/{id} without failure. |
| Fail |
Query fails, list is malformed, or navigation breaks. |
P0-02 - League create persists record
| Field |
Value |
| Type |
Functional + API |
| Description |
Creating a league should persist a new league record. |
| Verify |
UI + DevTools Network. Confirm leagueCreate succeeds. |
| Pass |
New league appears in list and details. |
| Fail |
Create response succeeds but record is missing, or mutation fails. |
P0-03 - League detail save persists edits
| Field |
Value |
| Type |
Functional + API |
| Description |
League metadata updates should save and persist on refresh. |
| Verify |
UI + DevTools Network. Confirm leagueUpdate succeeds. |
| Pass |
Edited values remain after refresh. |
| Fail |
Values revert or update mutation fails. |
P0-04 - Team associations can be managed
| Field |
Value |
| Type |
Functional |
| Description |
Teams tab should allow valid association updates for league hierarchy. |
| Verify |
UI only in Teams tab. |
| Pass |
Team links save and reload correctly. |
| Fail |
Association edits fail or are not retained. |
P1 - Core league flows
P1-01 - Search and sort remain stable
| Field |
Value |
| Type |
Functional + API |
| Description |
League search/sort controls should produce expected ordering/filtering. |
| Verify |
UI + DevTools Network (leagueList variables). |
| Pass |
Result set matches selected controls. |
| Fail |
Result ordering/filtering diverges from selected state. |
P1-02 - Metadata tab behavior remains stable
| Field |
Value |
| Type |
UI |
| Description |
Additional metadata section should render consistently for leagues. |
| Verify |
UI only. |
| Pass |
Metadata tab loads and remains usable. |
| Fail |
Tab is missing unexpectedly or fails at runtime. |
P2 - Secondary league checks
P2-01 - Unsupported actions remain hidden
| Field |
Value |
| Type |
UI |
| Description |
Non-applicable actions for current league status/role should not be exposed. |
| Verify |
UI only on two league rows with different statuses. |
| Pass |
Only valid actions are visible. |
| Fail |
Disallowed actions are visible or triggerable. |
P2-02 - Multi-tab edits do not drop context unexpectedly
| Field |
Value |
| Type |
UI |
| Description |
Switching between league tabs should not unexpectedly reset in-session edits. |
| Verify |
UI only. |
| Pass |
Unsaved field context remains stable in normal navigation. |
| Fail |
Values clear unexpectedly when changing tabs. |
P3 - Polish
P3-01 - League detail flow is console-clean
| Field |
Value |
| Type |
UI + API |
| Description |
Normal league interactions should not emit uncaught runtime errors. |
| Verify |
UI + DevTools Console during create/edit/save. |
| Pass |
No uncaught exceptions are logged. |
| Fail |
Console shows uncaught exceptions tied to league flow. |