View all services
Talk to QA Advisor
Browse the Knowledge Hub56 resources
/Test Cases/OTT video playback test cases

Test cases

OTT playback test cases, for everything after the first two minutes

Twenty eight cases covering adaptive bitrate recovery, DRM licence renewal mid stream, output protection, concurrent stream limits and leaked slots, geo and availability windows, resume position conflicts across devices, ad break cue points, subtitle and audio switching, offline download expiry and platform interruptions.

28cases/8coverage types/9boundary cases/FreeCSV download

All 28 test cases, ready to copy

Free to use and adapt, no sign-up. Download as CSV or Markdown, or copy it straight into your own tooling.

Last updated

28 worked examples

OTT-01

Start playback and measure time to first frame

TypePerformancePriorityHigh
Test data
Press play on a title on a stable connection at the target bandwidth
Expected result
First frame renders inside the stated budget, the initial rendition is chosen for fast start rather than maximum quality, and no black frame precedes audio.
OTT-02

Step down the bitrate ladder as bandwidth falls

TypePerformancePriorityHigh
Test data
Throttle from 10 Mbps to 800 kbps during playback
Expected result
Rendition steps down within a few segments and playback continues without stalling. A player that buffers rather than adapting has a broken ladder.
OTT-03

Recover the bitrate after bandwidth returns

TypePerformancePriorityHigh
Test data
Throttle to 800 kbps for two minutes, then restore full bandwidth
Expected result
Rendition climbs back within a bounded period. A ladder that steps down and never recovers leaves every viewer watching the lowest quality after one dip.
OTT-04

Survive a complete network drop and reconnect

TypeStatePriorityHigh
Test data
Disconnect for thirty seconds mid playback, then reconnect
Expected result
Player retries with backoff, resumes from the same position rather than restarting, and shows a recoverable state instead of a fatal error.
OTT-05

Acquire a DRM licence and refuse playback without one

TypeSecurityPriorityHigh
Test data
Play a protected title, then attempt playback with the licence request blocked
Expected result
Playback proceeds in the first case and is refused with a distinct error in the second. Protected content never falls back to an unprotected stream.
OTT-06

Renew a DRM licence that expires mid playback

TypeBoundaryPriorityHigh
Test data
A title longer than the licence duration, watched continuously past the expiry point
Expected result
Licence renews without interrupting playback. This is the defect that only appears on long content and is missed by testing the first two minutes.
OTT-07

Enforce output protection on external displays

TypeSecurityPriorityHigh
Test data
Play premium content over a connection that does not support the required protection level
Expected result
Playback is blocked or downgraded to the permitted resolution according to the rights agreement, with a message that explains the restriction.
OTT-08

Restrict the maximum resolution by plan and device

TypeFunctionalPriorityHigh
Test data
A plan capped at standard definition on a device capable of ultra high definition
Expected result
Ladder is capped server side. A cap applied only in the client is bypassed by requesting the higher rendition directly.
OTT-09

Enforce the concurrent stream limit

TypeBoundaryPriorityHigh
Test data
Plan allows two streams. Start a third, then start two simultaneously from two devices
Expected result
Third is refused with a clear message naming the limit, and the simultaneous case resolves to exactly two rather than allowing three through a race.
OTT-10

Release a stream slot when playback ends abnormally

TypeStatePriorityHigh
Test data
Force kill the app mid playback, then start a stream elsewhere
Expected result
Slot is released within the stated heartbeat window. A slot that leaks locks paying subscribers out of their own account.
OTT-11

Refuse playback outside the licensed territory

TypeSecurityPriorityHigh
Test data
Request a geo restricted title from an out of territory address and through a proxy
Expected result
Refused with a geo specific message, and the check is applied at licence issue rather than only at the catalogue listing.
OTT-12

Honour the availability window for a title

TypeBoundaryPriorityHigh
Test data
A title one minute before its release time and one minute after its expiry
Expected result
Refused in both cases in the correct timezone, and an in progress stream at the expiry boundary is handled according to the documented rule.
OTT-13

Save and restore the resume position on the same device

TypeStatePriorityHigh
Test data
Watch to 12 minutes 30 seconds, close the app, reopen the title
Expected result
Resumes within the stated tolerance of the saved position, and the position is saved periodically rather than only on a clean exit.
OTT-14

Reconcile resume positions across two devices

TypeBoundaryPriorityHigh
Test data
Watch to 20 minutes on one device, then to 10 minutes on another while the first is offline
Expected result
Documented conflict rule is applied consistently rather than the last write winning silently, and the viewer is not sent back to an earlier point without explanation.
OTT-15

Mark a title as watched at the correct threshold

TypeBoundaryPriorityMedium
Test data
Stop just before the completion threshold, then just after, then skip to the credits
Expected result
Completion is recorded only past the threshold, and skipping to the end does not mark the episode watched if the policy requires actual viewing.
OTT-16

Seek accurately forwards and backwards

TypeFunctionalPriorityHigh
Test data
Seek to the last second, the first second, and repeatedly scrub across a segment boundary
Expected result
Playback lands within tolerance of the requested position every time, audio and video remain in sync, and rapid scrubbing does not leave the player stalled.
OTT-17

Keep audio and video in sync after an interruption

TypeFunctionalPriorityHigh
Test data
Resume after a rendition switch, after an advertisement break and after a network recovery
Expected result
Sync is maintained in all three cases. Drift that appears only after an interruption is the most commonly reported and least commonly tested playback defect.
OTT-18

Insert an advertisement break and return to content

TypeStatePriorityHigh
Test data
A mid roll break, then a break where the advertisement fails to load
Expected result
Content resumes at the exact cue point in both cases. A failed advertisement must not consume the break slot silently or leave the player stuck.
OTT-19

Prevent seeking past an unwatched advertisement break

TypeNegativePriorityMedium
Test data
Seek beyond an unplayed mid roll cue point
Expected result
Player returns to the cue point according to the documented rule rather than allowing the break to be skipped by scrubbing.
OTT-20

Switch subtitle tracks during playback

TypeFunctionalPriorityHigh
Test data
Switch between two languages and off, mid playback and immediately after a seek
Expected result
Correct track renders in sync within a second, the previous track is removed, and no duplicate captions are displayed simultaneously.
OTT-21

Render subtitle characters and positioning correctly

TypeCompatibilityPriorityMedium
Test data
Tracks with accented characters, right to left script, and cues positioned to avoid burned in text
Expected result
Characters render without substitution, direction is correct, and positioning is honoured rather than every cue being forced to the bottom centre.
OTT-22

Switch audio tracks and preserve the selection

TypeStatePriorityMedium
Test data
Select an alternative language and a described audio track, then play the next episode
Expected result
Selection persists across episodes where the policy says so, and falls back predictably when the chosen track is absent from a title.
OTT-23

Download for offline playback and play without a connection

TypeFunctionalPriorityHigh
Test data
Download a title, enable flight mode, play it
Expected result
Plays fully offline including subtitles and the selected audio track, and the resume position is stored locally and synced on reconnection.
OTT-24

Expire an offline download at the end of its licence

TypeBoundaryPriorityHigh
Test data
A download played one hour before its expiry and one hour after, both while offline
Expected result
Plays before expiry and is refused after it. An offline licence that never expires because the device cannot be reached is a rights exposure.
OTT-25

Handle interrupted and resumed downloads

TypeStatePriorityMedium
Test data
Interrupt a download at 60 per cent, resume it, and fill the device storage during a download
Expected result
Resumes from the interruption point rather than restarting, and a storage failure produces a clear message with no unplayable partial file left behind.
OTT-26

Handle interruptions from the operating system

TypeStatePriorityHigh
Test data
An incoming call, a headphone disconnect, backgrounding the app and a device lock during playback
Expected result
Playback pauses and resumes according to platform convention, audio does not continue after a headphone disconnect, and the position is not lost.
OTT-27

Report playback telemetry accurately

TypeStatePriorityMedium
Test data
A session with two rendition switches, one stall, one seek and an abandoned start
Expected result
Reported watch time, stall count and abandonment match what actually happened, since these figures drive both rights reporting and engineering decisions.
OTT-28

Operate the player with a keyboard, remote and screen reader

TypeAccessibilityPriorityHigh
Test data
Keyboard and directional remote navigation through play, seek, subtitle and audio controls
Expected result
Every control is reachable and labelled, focus is visible on a television at viewing distance, and subtitle settings are announced and adjustable.

What goes in each field

ID

Required

Stable identifier, prefixed by module.

Test case

Required

What is being verified, in one line.

Type

Functional, negative, boundary, security, state, performance, accessibility or compatibility. Use it to check coverage is spread rather than clustered on the happy path.

Priority

Risk based, weighted by churn and by rights exposure. Anything that stops playback, plays content the viewer is not entitled to, or loses the resume position is High. Subtitle and audio failures are High in regulated markets.

Test data

The specific values, including the invalid and boundary ones.

Expected result

Required

The precise observable outcome, including message text where the wording itself is the requirement.

How To Use This

Throttle the connection, then restore it

Playback tests pass on a good connection on a new device. These four conditions are where subscribers actually churn.

Restore the bandwidth, not just remove it

Most sets check that quality drops under throttling. The defect is the ladder that steps down and never climbs back, leaving every viewer on the lowest rendition after one dip.

Watch past the licence duration

A DRM licence shorter than the title expires mid stream. Testing the opening minutes of a feature length film will never reach the point where renewal happens.

Kill the app and count the slots

Force stop mid playback, then start a stream elsewhere. A stream slot that leaks locks paying subscribers out of the account they are paying for.

Create a resume conflict deliberately

Watch to 20 minutes on one device and 10 on another while the first is offline. There has to be a documented rule, because last write wins sends viewers backwards.

What Most Sets Miss

Why playback defects drive churn

Adaptive bitrate is usually tested in one direction only. Throttling the connection and confirming that quality drops is the easy half; the half that matters is whether the ladder climbs back when bandwidth returns. A player that steps down under a brief dip and then stays there delivers the lowest rendition for the rest of the session, which viewers experience as a permanently blurry service rather than as a temporary network event. The recovery case takes two minutes to run and it is absent from almost every published set.

DRM fails on duration rather than on setup. Licence acquisition is tested constantly because nothing plays without it, but a licence whose duration is shorter than the title has to be renewed mid stream, and that path is only reachable by actually watching long enough. The related rights cases are output protection on an external display and the resolution cap by plan, and the cap has to be applied server side: a ladder limited only in the client is bypassed by requesting the higher rendition directly.

Concurrency has two failure modes that pull in opposite directions. A limit that is not enforced under simultaneous starts lets a third stream through a race, which is a rights problem. A slot that is not released when the app is force killed locks a paying subscriber out of their own account, which is a support problem and a far more common complaint. Both need testing, and the second one needs the abnormal exit rather than the clean one.

Resume position is where viewers notice sloppiness most sharply. It has to be saved periodically rather than on a clean exit, because the app being killed is the normal way playback ends on a phone. Across devices it becomes a conflict resolution problem, and there needs to be a documented rule rather than whichever write arrived last. The same care applies to the completion threshold: skipping to the credits should not mark an episode watched if the policy says otherwise, because that figure feeds both recommendations and rights reporting.

Suggest an improvement

Testing a streaming or OTT platform?

QAble tests playback across devices and networks, including adaptive bitrate behaviour, DRM and rights enforcement, concurrency limits and offline licensing.

OTT testing services

More test case sets

View all

Test cases for a login page

Test cases
25 cases across functional, negative, boundary, security, session and accessibility paths, including account enumeration and lockout.

Test cases for a registration form

Test cases
28 cases covering validation, duplicate accounts, email verification, password rules and the enumeration leak most signup forms ship with.

Test cases for search functionality

Test cases
28 cases across relevance, partial and fuzzy matching, filters, pagination, empty states, injection attempts and performance under load.

Test cases for a shopping cart

Test cases
27 cases on quantity limits, price recalculation, stock changes, coupon stacking, guest to account merge and cart persistence.

Test cases for checkout and payment

Test cases
30 cases including 3D Secure, declines, timeouts, duplicate charges, idempotency, refunds and partial captures.

Test cases for file upload

Test cases
28 cases on size and type limits, spoofed content types, malicious filenames, progress, resume, virus scanning and storage limits.

Test cases for forgot password

Test cases
26 cases on reset token expiry, single use enforcement, session invalidation and the enumeration and rate limit gaps that are routine here.

Test cases for OTP verification

Test cases
26 cases on expiry, resend throttling, attempt limits, code reuse, delivery failure and the brute force window teams forget to close.

Test cases for user roles and permissions

Test cases
26 cases on horizontal and vertical privilege checks, direct object access, role changes mid-session and permission inheritance.

Test cases for form validation

Test cases
27 rules-based cases on required fields, length and numeric boundaries, client and server parity, hidden field tampering and error accessibility.

Test cases for a date picker

Test cases
26 cases on timezone shifts, ambiguous day and month order, impossible dates, min and max limits, leap years and keyboard operation.

Test cases for pagination

Test cases
24 cases on ordering stability, records changing mid-session, page size caps, deep offset cost, permission-filtered totals and state restore.

Test cases for push notifications

Test cases
26 cases on app states, deep link routing, token release on sign out, lock screen privacy, preferences, provider failures and platform differences.

Test cases for reports and data export

Test cases
25 cases on permission filtering in the file, spreadsheet formula injection, encoding, typed numbers and dates, row limits and audit logging.

Test cases for a chatbot

Test cases
28 cases on paraphrased intents, context, fallback loops, human handoff, policy grounding, prompt injection and data scoping.

Test cases for net banking transactions

Test cases
28 cases on duplicate debits from a retried request, concurrent transfers against one balance, daily limits across channels, beneficiary cooling periods, second factor binding and reconciliation.

Test cases for wallet and UPI payments

Test cases
28 cases on payments that time out with no response, idempotency on retry, racing balances, caps across devices, collect request fraud, mandates and refunds.

Test cases for insurance claim submission

Test cases
28 cases on coverage at the date of loss, waiting periods, deductibles and sub limits, exclusions and riders, duplicate claims and settlement reconciliation.

Test cases for patient records in an EHR

Test cases
28 cases on duplicate detection and merge, wrong patient entry, units of measure, allergy and interaction alerting, break glass access and audit of reads.

Test cases for CRM lead management

Test cases
28 cases on duplicate leads under concurrency, routing and the unrouted fallback, round robin races, territory visibility, conversion and bulk import.

Test cases for an ERP purchase order

Test cases
28 cases on approval thresholds, amendments that must reset approval, budget commitment races, over receipt tolerance, three-way match and duplicate invoices.

Test cases for game level progression

Test cases
28 cases on save corruption during a crash write, cloud save conflicts, offline queue replay, unlock gating, currency exploits and purchase restore.

Test cases for a REST API

Test cases
28 cases on status code correctness, cross tenant resource access, mass assignment, idempotent retries, cursor pagination, rate limits and contract drift.

Test cases for SSO and social login

Test cases
28 cases on linking an account on an unverified email, state and code replay, redirect allow lists, token signature and issuer, deprovisioning and session rotation.

Test cases for subscription and billing

Test cases
28 cases on mid cycle proration, duplicate and out of order webhooks, renewal double charges, dunning and grace, trials, coupons, metered usage and tax.

Test cases for data tables, filters and sorting

Test cases
28 cases on unstable sorts across pages, filters that must reset pagination, selection surviving a filter change, bulk action scope and export fidelity.

Test cases for session timeout and concurrent login

Test cases
28 cases on tokens that survive sign out, refresh token reuse, idle against absolute lifetime, multi tab expiry, session limits and remote revocation.

Test cases for a multi step form wizard

Test cases
28 cases on values lost to back navigation, refresh and session expiry, step skipping, server side revalidation, duplicate submission and conditional branches.

Test cases for email verification

Test cases
28 cases on token reuse and expiry, invalidating earlier links, account enumeration, header injection, safe address change and mail scanner prefetching.

Test cases for dashboards and analytics widgets

Test cases
28 cases on reconciling against source rows, widgets that disagree, timezone aggregation, zero baselines, no data shown as zero and permission leaks in aggregates.

Test cases for booking and reservation

Test cases
28 cases on concurrent bookings for the last slot, inventory holds that leak, payment without a booking, cancellation boundaries and channel sync.

Test cases for mobile app install and update

Test cases
28 cases on migration chains across skipped versions, crashes during post upgrade migration, forced update lockouts, deep links and clean reinstall.

Test cases for accessibility (WCAG 2.2 AA)

Test cases
28 cases on keyboard only completion, focus management, live region announcements, contrast, reflow at 320 pixels, target size and screen reader verification.

Test cases for performance and load

Test cases
28 cases on spikes with no ramp, recovery after peak, soak and leak detection, pool exhaustion, cold caches, retry storms and data correctness under load.

Test cases for the OWASP Top 10

Test cases
28 cases on broken access control, mass assignment, injection across every input surface, credential stuffing, session invalidation, SSRF and exposed secrets.

Test cases for cross browser compatibility

Test cases
28 cases on storage that throws in private mode, blocked third party cookies, engine date parsing, mobile viewport units, in app browsers and ad blockers.

Test cases for database and data integrity

Test cases
28 cases on uniqueness under concurrency, lost updates, counter races, orphaned rows, migration and backfill safety, replica lag and verified restores.

Test cases for localisation and multi language support

Test cases
28 cases on text expansion, concatenated sentences, plural rules, locale date parsing, decimal separators, right to left layout, collation and encoding.

Want playback quality proven, not assumed?

QAble covers functional, performance and compatibility paths with ISTQB-certified engineers. Start with a free QA audit of your platform.

Talk to QA Advisor