Content Type QA - Live
Run common.md first. This file covers Live-specific behavior for /content/live and /content/live/{id}.
For deep internal provisioning rules and payload-level guard rails, also run Internal Live Create.
Totals
| Priority |
Count |
| P0 |
7 |
| P1 |
8 |
| P2 |
3 |
| P3 |
1 |
| Total |
19 |
CREATE FLOW
Use this section for Live-only create checks. Shared create expectations (modal open, generic create persistence, shared validation behavior) are covered in common.md.
P0 - Release blockers
C-P0-01 - Live create branch selection works
| Field |
Value |
| Type |
Functional |
| Description |
Live create must expose both Internal Live Stream Service and Third Party Live Stream (HLS) branches. |
| Verify |
UI only. Open both create branches and validate baseline controls render. |
| Pass |
Both branches are reachable and interactive without runtime failure. |
| Fail |
One branch is missing, broken, or unusable. |
C-P0-02 - Internal create persists through mutation
| Field |
Value |
| Type |
Functional + API |
| Description |
A valid Internal Live create must persist and produce a retrievable Live item. |
| Verify |
UI + DevTools Network. Confirm liveVideoCreate succeeds for an Internal branch submission. |
| Pass |
New Live record is created and opens in details/list successfully. |
| Fail |
Create fails, returns GraphQL errors, or reports false success. |
C-P0-03 - Third-party HLS create persists through mutation
| Field |
Value |
| Type |
Functional + API |
| Description |
A valid Third Party Live Stream (HLS) create must persist correctly. |
| Verify |
UI + DevTools Network. Submit minimum valid third-party fields and confirm create success response. |
| Pass |
New Live record from third-party path is created and retrievable. |
| Fail |
Third-party branch submission fails or creates an unusable record. |
P1 - Core create checks
C-P1-01 - Internal create validation blocks incomplete submissions
| Field |
Value |
| Type |
Functional |
| Description |
Required internal create inputs must prevent invalid submit attempts. |
| Verify |
UI only. Attempt submit with missing region/protocol and one incomplete provider-specific dependency. |
| Pass |
Validation feedback appears and invalid submit is blocked. |
| Fail |
Submit proceeds with incomplete required data. |
C-P1-02 - AWS and Harmonic minimal happy paths remain healthy
| Field |
Value |
| Type |
Functional + API |
| Description |
Internal create should remain reliable for both AWS and Harmonic provider paths. |
| Verify |
UI + DevTools Network. Execute one valid minimal create for AWS and one for Harmonic (where environment supports both). |
| Pass |
Both provider submissions complete with successful create responses. |
| Fail |
One provider path fails with valid inputs. |
C-P1-03 - Existing source/input discovery calls populate selectors
| Field |
Value |
| Type |
API |
| Description |
Internal create should resolve source/input selectors when existing topology toggles are enabled. |
| Verify |
DevTools Network. Confirm liveSourceList and liveInputList complete successfully when applicable. |
| Pass |
Existing source/input selectors populate from successful responses. |
| Fail |
Selectors remain empty due to failed discovery requests or schema mismatch. |
P2 - Secondary create checks
C-P2-01 - Provider and mode switches do not leak incompatible values
| Field |
Value |
| Type |
Functional |
| Description |
Switching provider/protocol modes should not submit stale incompatible values. |
| Verify |
UI only. Fill advanced fields in one mode, switch mode/provider, and submit a valid minimal config. |
| Pass |
Submission reflects current mode requirements only and succeeds when valid. |
| Fail |
Hidden stale values break submit or produce invalid payload behavior. |
DETAIL VIEW FLOW
Use this section for the Live Stream detail control surface (Live Stream tab) after a Live item exists.
P0 - Release blockers
D-P0-01 - Live Stream detail control surface loads
| Field |
Value |
| Type |
Functional |
| Description |
Live details must render the control surface card and the Stream/Monitoring tabs without runtime failure. |
| Verify |
UI only on /content/live/{id}. Open the Live Stream tab and switch between Stream and Monitoring. |
| Pass |
Control surface card and both tabs render and remain interactive. |
| Fail |
Tab content is missing, blank, or crashes. |
D-P0-02 - Publish-before-start gate is enforced
| Field |
Value |
| Type |
Functional |
| Description |
Start Live Stream should be blocked when content is not in a publish-ready state. |
| Verify |
UI only. Attempt Start on an unpublished Live item. |
| Pass |
Start is blocked with clear feedback and no invalid start action is sent. |
| Fail |
Start action proceeds from an invalid publish state. |
D-P0-03 - Start and Stop actions refresh status correctly
| Field |
Value |
| Type |
Functional + API |
| Description |
Start/Stop actions must invoke runtime action flow and reflect updated state after refresh/poll. |
| Verify |
UI + DevTools Network. Trigger Start or Stop and confirm follow-up status fetch/update behavior succeeds. |
| Pass |
Action completes, status updates, and refreshed state matches action outcome. |
| Fail |
Action appears successful but state does not update, or request fails. |
D-P0-04 - Channel status presentation matches backend runtime state
| Field |
Value |
| Type |
UI + API |
| Description |
Channel status/workflow metadata in the control-surface card must track latest backend state. |
| Verify |
UI + DevTools Network. Confirm liveVideoGet (and follow-up status polling) succeeds while status panel updates. |
| Pass |
Status panel reflects expected state metadata without stale contradictions. |
| Fail |
Status panel is stale/empty despite successful responses, or query fails. |
P1 - Core detail checks
D-P1-01 - Stream inputs render copyable ingest and egress fields
| Field |
Value |
| Type |
Functional |
| Description |
Stream tab should show primary/secondary input details (URL, stream ID, egress, bitrate) with copy affordances. |
| Verify |
UI only. Inspect rows for populated values and exercise copy actions. |
| Pass |
Expected values render and copy actions work per available row fields. |
| Fail |
Required fields are missing, mislabeled, or copy actions fail. |
D-P1-02 - Harmonic audio grooming flow remains operational
| Field |
Value |
| Type |
Functional + API |
| Description |
Harmonic stream rows should support connect/discover/select/update and input Start/Stop controls. |
| Verify |
UI + DevTools Network on eligible Harmonic items. Trigger connect/discover/update and input state actions. |
| Pass |
Grooming actions complete with expected state transitions and successful service responses. |
| Fail |
Grooming flow stalls, errors, or leaves rows in unrecoverable state. |
D-P1-03 - Monitoring tab alerts and refresh behavior remain stable
| Field |
Value |
| Type |
Functional + API |
| Description |
Monitoring tab should display media alerts and allow manual refresh without breaking table state. |
| Verify |
UI + DevTools Network. Confirm alerts query/poll returns data and refresh action succeeds. |
| Pass |
Alerts render correctly and Refresh Alerts updates data without runtime errors. |
| Fail |
Alerts do not load, refresh fails, or table becomes inconsistent. |
D-P1-04 - Quick settings update behavior matches editability rules
| Field |
Value |
| Type |
Functional + API |
| Description |
Quick settings must allow intended edits (for example DVR/SSAI) and preserve read-only presentation for non-editable settings (for example Low Latency/DRM). |
| Verify |
UI + DevTools Network. Edit allowed fields and save; validate read-only fields remain non-editable. |
| Pass |
Editable fields persist successfully and read-only fields stay protected. |
| Fail |
Editable fields do not persist, or read-only controls become mutable. |
D-P1-05 - Live detail save persists stream configuration changes
| Field |
Value |
| Type |
Functional + API |
| Description |
Valid detail edits tied to live stream configuration should persist across refresh. |
| Verify |
UI + DevTools Network. Confirm liveVideoUpdate (or equivalent detail update) succeeds and refresh preserves changes. |
| Pass |
Updated values remain after refresh with successful network contract. |
| Fail |
Save appears successful but values revert or update request fails. |
P2 - Secondary detail checks
D-P2-01 - Archive chooser actions remain reliable
| Field |
Value |
| Type |
Functional + API |
| Description |
Archive chooser should support preview, download, and convert-to-VOD actions when eligible. |
| Verify |
UI + DevTools Network. Open Choose Archive, run preview/download on one row, and trigger convert flow. |
| Pass |
Actions complete as expected; convert flow routes to created VOD without destructive side effects. |
| Fail |
Archive actions fail, produce broken links, or conversion workflow breaks. |
D-P2-02 - Workflow and CloudFront progress surfaces stay coherent
| Field |
Value |
| Type |
UI + API |
| Description |
Runtime workflow messaging, CloudFront progress hints, and scheduled/processing start gating should remain consistent with backend state. |
| Verify |
UI + DevTools Network while state transitions occur. |
| Pass |
Banners, status hints, and start gating reflect current runtime conditions. |
| Fail |
Progress/state messages conflict with backend state or gating rules misfire. |
P3 - Polish
D-P3-01 - No uncaught console errors during core Live create/detail paths
| Field |
Value |
| Type |
UI + API |
| Description |
Normal Live create and detail interactions should remain free of uncaught client exceptions. |
| Verify |
UI + DevTools Console across create branch selection, create submit, Live Stream tab actions, and save. |
| Pass |
No uncaught exceptions tied to Live flow interactions. |
| Fail |
Console reports runtime exceptions or unhandled promise rejections during normal flow. |