Content Type QA - Article
Run common.mdfirst. This file covers Article-specific behavior for /content/article and /content/article/{id}.
Totals
| Priority |
Count |
| P0 |
4 |
| P1 |
4 |
| P2 |
2 |
| P3 |
1 |
| Total |
11 |
P0 - Release blockers
P0-01 - Article list query and detail navigation
| Field |
Value |
| Type |
Functional + API |
| Description |
Article list must load and route correctly to article details. |
| Verify |
UI + DevTools Network. Confirm articleList succeeds. |
| Pass |
Rows load and row click opens /content/article/{id}. |
| Fail |
Query fails, list is empty unexpectedly, or route open fails. |
P0-02 - Article create persists with required fields
| Field |
Value |
| Type |
Functional + API |
| Description |
Creating an article with required fields should produce a persistent record. |
| Verify |
UI + DevTools Network. Confirm articleCreate succeeds. |
| Pass |
New article is visible in list/details with valid ID. |
| Fail |
Success feedback appears without persisted record, or mutation errors. |
P0-03 - Editor content can be saved and reloaded
| Field |
Value |
| Type |
Functional |
| Description |
Rich text editor content in Article details must persist after save and refresh. |
| Verify |
UI only in Editor tab. |
| Pass |
Saved content reloads exactly as expected. |
| Fail |
Content is lost, malformed, or editor fails on open/save. |
P0-04 - Article update mutation persists metadata changes
| Field |
Value |
| Type |
Functional + API |
| Description |
Metadata changes in Article details should persist through update flow. |
| Verify |
UI + DevTools Network. Confirm articleUpdate succeeds. |
| Pass |
Updated fields remain after refresh and state transition is correct. |
| Fail |
Changes revert, update fails, or save success is false-positive. |
P1 - Core Article flows
P1-01 - SEO tab behavior is stable
| Field |
Value |
| Type |
Functional |
| Description |
SEO metadata fields should save and reload without data loss. |
| Verify |
UI only in SEO tab. |
| Pass |
Edited SEO values persist correctly. |
| Fail |
Values are dropped, malformed, or not reloadable. |
P1-02 - Photo Gallery tab linkage works
| Field |
Value |
| Type |
Functional |
| Description |
Photo gallery associations in Article details should be editable and persistent. |
| Verify |
UI only in Photo Gallery tab. |
| Pass |
Added/removed links persist after save and refresh. |
| Fail |
Changes do not persist or tab actions fail. |
P1-03 - Availability scheduling behaves consistently
| Field |
Value |
| Type |
Functional |
| Description |
Article availability window updates should be validated and saved correctly. |
| Verify |
UI only in Availability & Scheduling tab. |
| Pass |
Window updates persist and are reflected in status behavior. |
| Fail |
Invalid window accepted or valid window not retained. |
P1-04 - Publish and preview flow works for eligible article
| Field |
Value |
| Type |
Functional |
| Description |
Published article should support preview and consistent state transitions. |
| Verify |
UI only, plus optional network check on articleUpdate. |
| Pass |
Preview opens expected destination and state remains valid after refresh. |
| Fail |
Preview unavailable for eligible state or routes incorrectly. |
P2 - Secondary Article checks
P2-01 - Duplicate action creates isolated draft
| Field |
Value |
| Type |
Functional |
| Description |
Duplicate should create a new article draft and preserve source record unchanged. |
| Verify |
UI only. |
| Pass |
New article ID is created and editable independently. |
| Fail |
Source content mutates or duplicate fails silently. |
P2-02 - Additional metadata tab consistency
| Field |
Value |
| Type |
UI |
| Description |
Metadata and macros fields should remain visible and stable for configured sites. |
| Verify |
UI only. |
| Pass |
Tab renders expected controls with no runtime instability. |
| Fail |
Controls disappear unexpectedly or tab crashes. |
P3 - Polish
P3-01 - Editor toolbar interactions do not produce console exceptions
| Field |
Value |
| Type |
UI + API |
| Description |
Routine editor actions should not trigger uncaught console/runtime errors. |
| Verify |
UI + DevTools Console while editing and saving article body. |
| Pass |
No uncaught exceptions are emitted during normal editing. |
| Fail |
Runtime or promise errors appear from editor interactions. |