Content Type QA - Linear Channel
Run common.md first. This file covers Linear Channel behavior for /content/linearchannel and /content/linearchannel/{id}.
Totals
| Priority |
Count |
| P0 |
4 |
| P1 |
3 |
| P2 |
2 |
| P3 |
1 |
| Total |
10 |
P0 - Release blockers
P0-01 - Linear channel list and details load
| Field |
Value |
| Type |
Functional + API |
| Description |
Linear channel list must load and navigate to detail pages correctly. |
| Verify |
UI + DevTools Network. Confirm linearchannelList succeeds. |
| Pass |
Rows render and open /content/linearchannel/{id} without errors. |
| Fail |
Query fails, row mapping breaks, or navigation fails. |
P0-02 - Linear channel create persists record
| Field |
Value |
| Type |
Functional + API |
| Description |
Creating a linear channel should persist a new content item. |
| Verify |
UI + DevTools Network. Confirm linearchannelCreate succeeds. |
| Pass |
Created record is visible and editable in details. |
| Fail |
Create shows success without persisted record, or mutation fails. |
P0-03 - Linear channel detail save persists updates
| Field |
Value |
| Type |
Functional + API |
| Description |
Metadata and channel-specific edits must persist through save. |
| Verify |
UI + DevTools Network. Confirm linearchannelUpdate succeeds. |
| Pass |
Updated values remain after refresh. |
| Fail |
Values revert or update request fails. |
P0-04 - Publish/unpublish transitions remain valid
| Field |
Value |
| Type |
Functional + API |
| Description |
Header/list state actions should move linear channel through valid states. |
| Verify |
UI + DevTools Network (linearchannelUpdate action payload). |
| Pass |
Correct final status is shown and persists after reload. |
| Fail |
Wrong status transition or failed mutation. |
P1 - Core linear channel flows
P1-01 - Channels tab behavior and persistence
| Field |
Value |
| Type |
Functional |
| Description |
Channels tab should load and persist channel linkage/configuration changes. |
| Verify |
UI only in Channels tab. |
| Pass |
Changes save and are retained after refresh. |
| Fail |
Tab changes are lost or tab is non-functional. |
P1-02 - Monetization overrides tab behavior
| Field |
Value |
| Type |
Functional |
| Description |
Monetization overrides should save and apply expected override metadata. |
| Verify |
UI only in Monetization Overrides tab. |
| Pass |
Override edits persist and reload correctly. |
| Fail |
Overrides are not saved or render incorrectly after reload. |
P1-03 - Duplicate action creates separate draft
| Field |
Value |
| Type |
Functional |
| Description |
Duplicate action should create a new draft without mutating source channel. |
| Verify |
UI only. |
| Pass |
New ID is generated and source remains unchanged. |
| Fail |
Source mutates or duplicate fails silently. |
P2 - Secondary linear channel checks
P2-01 - List search/sort consistency
| Field |
Value |
| Type |
Functional + API |
| Description |
Search and sort controls should return predictable channel results. |
| Verify |
UI + DevTools Network (linearchannelList variables). |
| Pass |
Results align with selected controls. |
| Fail |
Controls update but output remains stale or inconsistent. |
P2-02 - Unsupported tabs are not exposed
| Field |
Value |
| Type |
UI |
| Description |
Tabs not part of linear channel contract should remain hidden. |
| Verify |
UI only in details sidebar. |
| Pass |
Only configured tabs are visible. |
| Fail |
Unsupported tabs appear and fail on access. |
P3 - Polish
P3-01 - Linear channel detail interactions are console-clean
| Field |
Value |
| Type |
UI + API |
| Description |
Normal tab interactions and saves should not emit uncaught console exceptions. |
| Verify |
UI + DevTools Console. |
| Pass |
No uncaught runtime errors in standard flow. |
| Fail |
Console shows uncaught exceptions tied to linear channel actions. |