Follow a section specific to your platform to perform the development validation tests.

Web platform tests

• For production deployments, use NPM distribution. The CDN distribution is not intended for production due to rate limiting when bandwidth usage exceeds a fair usage policy.
• Make sure to allow-list the domain of your website. To allow-list your domains, go to Bitmovin Dashboard > Player > Licenses, and select the player license you want to use.

Development prerequisites for moving to Phase 2 validation :

1. Bitmovin Web Player license/key and SDK version is selected.
   1. The video player version is printed in the web console.
   2. The event licensevalidated is triggered when the player is initialized.
2. Test environments: Dev, QA, Staging, Production (canary and full).
3. Test accounts if used for DRM provider, ad server (VAST/SSAI), and analytics endpoints.
4. Test streams and assets:
   1. VOD: HLS .m3u8 and DASH .mpd sample files (multiple bitrates, multiple audio tracks, caption tracks).
   2. Live: HLS and DASH live manifests (with DVR window).
   3. Low latency live test stream (LL‑HLS or CMAF/LL‑DASH, if available).
   4. Test ad creatives (VAST XML) and SSAI manifests, if used.
   5. Protected assets for each DRM system you use (Widevine, PlayReady, FairPlay) with test licenses.
   6. Browser matrix for testing (Chrome, Firefox, Safari, Edge; mobile Safari and Chrome on Android). Include specific browser versions used in production.
5. Network shaping tools for emulating bandwidth/latency/loss (for example, Charles, Browser devtools throttling).
6. Logging and monitoring (player logging enabled, network HAR capture capability, analytics event capture).

Android tests

Follow the testing process described on Migrating from ExoPlayer to the Bitmovin Player .

iOS tests

Follow the testing process described on Migrating from AVPlayer to the Bitmovin Player .