Content Core QA Checklists
Concise release checklists for content paths and features. Use these for final pass/fail QA decisions, with explicit P0-P3 outcomes and network verification notes.
How to use this set
- Run
common.md first.
- Run only the content-type files included in release scope.
- Mark pass/fail exactly as written; any fail in P0 should block release.
Priority scale
| Priority |
Meaning |
| P0 |
Release blocker for content operations (load/create/save/publish/list). |
| P1 |
Core type-specific user flows and high-impact tabs. |
| P2 |
Secondary behavior, edge flows, and fallback states. |
| P3 |
Low-risk polish and non-blocking quality checks. |
Verification types
| Type |
Use when |
Functional |
Business behavior is validated by user action and state outcome. |
UI |
Presentation, state visibility, and interaction behavior are validated. |
API |
Network contract is validated in DevTools (request + response). |
Functional + API |
Business flow must be confirmed with matching network behavior. |
UI + API |
UI behavior is coupled to a network response contract. |
Checklist index
Common first
Primary release surface
- VOD
- Live
- Series
- Article
- Video Playlist
- Collection
Sports and schedule surface
- Game
- Event
- Schedule
- Sport
- League
- Team
- Venue
Metadata and people
- Tag
- Category
- Person
- Badge
Media and utility types
- Image
- Audio
- Photo Gallery
- Linear Channel
- Feed
Notes for release triage
- A P0 failure in any in-scope type is a release blocker.
- If UI passes but required network operation is missing or returns GraphQL
errors, mark fail.
- For Live create depth cases, run the detailed companion checklist: Internal Live Create.
- For Live detail control-surface depth, use the
DETAIL VIEW FLOW section in Live.