Agree the test scope and acceptance criteria
Specify the events, test dates, regions, devices, player versions and delivery method. Ask for an evaluation window long enough to observe the agreed use case, including a full event when continuity is material. Establish pass/fail thresholds before testing.
Recorded demos are useful for reviewing selected picture content, but they cannot establish live latency, uptime or capacity. Test the actual evaluation feed in the environment you plan to operate, and separate content rights verification from technical acceptance.
Record measurements with their conditions
Use the same test procedure for each candidate feed. Record the source/event, time, network, region, device and player build beside every result. A single successful play does not prove continuous availability.
| Check | How to record it | Important distinction |
|---|---|---|
| Start-up | Time from play request to first displayed frame | Different from live end-to-end latency |
| Picture and audio | Delivered resolution/frame rate, dropped frames and A/V alignment | A nominal 1080P label is not a motion-quality result |
| Buffering | Number and total duration of rebuffering events over the test window | Always report the observation duration |
| Latency | Source-to-screen delay with a known reference and sample count | State measurement method and network conditions |
| Recovery | Time and result after a controlled connection interruption | Verify the recovered stream is still the correct event |
Test capacity only within the agreed limits
Confirm the permitted concurrent feeds and evaluation traffic before generating load. Test your CDN and player distribution path separately from provider ingest capacity. Do not run unapproved stress tests against a supplier endpoint.
Check overlapping events, URL expiry, refreshed credentials and an ended event. Confirm how errors are communicated and who handles a source interruption. Record whether recovery is automatic or requires manual intervention.
Ask for verifiable commercial and rights information
Before purchase, request the actual signing entity, service contract, support scope, pricing basis, payment/refund terms and distribution limits. Where a reference or case study is offered, confirm that it describes a real deployment and can be shared with permission.
Verify content source, territory, permitted platforms and any onward-distribution rights separately. Technical access does not include copyright licensing. Do not treat a league logo, an example URL or a recorded clip as evidence of rights.
Keep a redacted evaluation record
Summarise the test window, expected thresholds, observations, failures and unresolved questions. Include player logs or screenshots only when permitted and redact API tokens, signed playback URLs and personal information.
Use the record to agree the final scope with sales. If a key condition cannot be reproduced, mark it unverified rather than passed. Retest material changes to the delivery path before launching public playback.