Content Type QA - Collection
Run common.mdfirst. This file covers Collection-specific behavior for /content/collection and /content/collection/{id}.
Totals
| Priority |
Count |
| P0 |
4 |
| P1 |
3 |
| P2 |
2 |
| P3 |
1 |
| Total |
10 |
P0 - Release blockers
P0-01 - Collection list and detail route load
| Field |
Value |
| Type |
Functional + API |
| Description |
Collection list must load and open details reliably. |
| Verify |
UI + DevTools Network. Confirm collectionList succeeds. |
| Pass |
Rows render and open /content/collection/{id} without errors. |
| Fail |
Query fails, data mapping breaks list, or row open fails. |
P0-02 - Collection create persists new record
| Field |
Value |
| Type |
Functional + API |
| Description |
Creating a collection should persist a new content record. |
| Verify |
UI + DevTools Network. Confirm collectionCreate succeeds. |
| Pass |
New collection appears in list and detail opens successfully. |
| Fail |
Create success is false-positive or mutation errors occur. |
P0-03 - Collection detail save persists edits
| Field |
Value |
| Type |
Functional + API |
| Description |
Collection metadata edits should persist through save. |
| Verify |
UI + DevTools Network. Confirm collectionUpdate succeeds. |
| Pass |
Edited values remain after refresh. |
| Fail |
Values revert or save request fails. |
P0-04 - Publish state transition works
| Field |
Value |
| Type |
Functional + API |
| Description |
Collection publish/unpublish transitions must behave correctly. |
| Verify |
UI + DevTools Network (collectionUpdate action payload). |
| Pass |
Status changes and persists as expected. |
| Fail |
Wrong state change, disabled controls, or mutation errors. |
P1 - Core Collection flows
P1-01 - Multi-View tab supports configured layouts
| Field |
Value |
| Type |
Functional |
| Description |
Multi-View tab should load and allow valid configuration updates. |
| Verify |
UI only in Multi-View tab. |
| Pass |
Changes save and render after refresh. |
| Fail |
Tab fails to load or changes are not retained. |
P1-02 - Availability tab persistence
| Field |
Value |
| Type |
Functional |
| Description |
Collection availability windows should save/reload consistently. |
| Verify |
UI only in Availability & Scheduling tab. |
| Pass |
Window changes persist and reflect expected state. |
| Fail |
Window values are lost or invalid values are accepted. |
P1-03 - SEO tab behavior remains stable
| Field |
Value |
| Type |
Functional |
| Description |
SEO settings should be editable and persist for collection content. |
| Verify |
UI only in SEO tab. |
| Pass |
SEO values persist after refresh. |
| Fail |
SEO edits are dropped or detail page becomes unstable. |
P2 - Secondary Collection checks
P2-01 - No unsupported version history expectation
| Field |
Value |
| Type |
UI |
| Description |
Collection should not expose unsupported version history tab if backend support is absent. |
| Verify |
UI only in details sidebar. |
| Pass |
Version history tab visibility matches current support contract. |
| Fail |
Unsupported tab appears and fails at runtime. |
P2-02 - Search/sort consistency on curated collections
| Field |
Value |
| Type |
Functional + API |
| Description |
Search and sort should remain predictable for large curated collections. |
| Verify |
UI + DevTools Network (collectionList variables). |
| Pass |
Ordering/filtering follows selected controls. |
| Fail |
Returned ordering/filtering deviates from selected criteria. |
P3 - Polish
P3-01 - Collection detail tab switching is console-clean
| Field |
Value |
| Type |
UI + API |
| Description |
Navigating tabs and saving in collection details should not log uncaught exceptions. |
| Verify |
UI + DevTools Console. |
| Pass |
No uncaught runtime errors in normal detail interactions. |
| Fail |
Console logs uncaught exceptions from collection flow. |