Missed Part 1 of OTT Testing Made Easy? Catch up, here.

Part 1 was all about what the user sees – design, layout, navigation, speed. But great OTT platforms aren’t just built on what looks good. They’re held together by what works behind the scenes. 

In Part 2, we’re getting into the details that make or break everyday use: payments that go through without a problem, profiles that work across devices, content that’s locked to the right regions, and data that helps you improve the experience over time.

This is the part of testing that doesn’t always get talked about, but absolutely can’t be missed.

Here’s a look at what’s covered:

• Subscription and Payment Testing
• Security and DRM Testing
• Profile/Age Restriction Testing
• Geoblock and VPN Testing
• Analytics
• Installation/Uninstallation/Updates

Subscription and Payment Testing

The majority of OTT apps offer some free content, whereas premium content is behind a paywall. Different providers use several subscription models, including AVOD, SVOD, and TVOD. 

• AVOD provides users with a catalogue of on-demand content containing video advertisements.
  
• SVOD grants access to an entire library of videos or content for a fixed, recurring fee.
  
• TVOD lets users buy or rent individual pieces of content, such as Google Play Movies, BookMyShow or pay per view.

At DIAGNAL, we have applications in each of these categories. For efficient coverage, we ensure that:

• Premium content is only available to active subscribers.
• Payment methods vary by region and include in-app payments, debit/credit cards, PayPal, and Apple Pay. Payment failure scenarios should display user-friendly messages with retry options, for example, when there are network issues or incorrect card details.
• If auto-renewal succeeds, users retain access to premium content; it fails if the card has expired or been deactivated.
• Upon subscription expiration, app access continues to work correctly.
• The payment process must be secure.
• A user who subscribes on one device should be able to access premium content on other devices with the same account.
• For AVOD, users can skip ads or must watch the full ad, based on configuration.
• Users migrating from other systems should have their subscription status and payment schedule transferred seamlessly.

Security and DRM Testing

When assessing the security level of an OTT platform, we evaluate the app for vulnerabilities, such as data breaches, unauthorised access, piracy, and failures in content protection. 

This approach ensures that user feedback, data and content remain safe from potential threats and attacks. For many of our projects at DIAGNAL, we follow the OWASP checklists for web and native applications. 

Security measures include the following checkpoints:

• Ensure that no user data is shared in unencrypted format in any API response, and that all API requests and responses during a payment flow are encrypted.

• Verify that non-admin users cannot access areas of the application meant for admin access.
  
• Store card details in encrypted format only if the end user has given permission to do so.
  
• Save user passwords in encrypted format.
  
• Ensure all API calls retrieving sensitive information are strictly authenticated.
  
• Set authentication tokens to expire within a reasonable timeframe.
  

DRM (Digital Rights Management), on the other hand, uses methods to protect content from piracy and unauthorised access. To verify this, we can:

• Attempt to take a screenshot of the video as it plays – the player area should appear black and content must remain hidden. 

• Try to record the screen during playback – the player area should show an error or remain blank.
  
• Attempt to share your screen on platforms like Google Meet or Slack Huddles – the Player area should show an error or stay blank.
  
• Test the DRM implementation according to the content’s protection level. 

• Use an expired or outdated license token when calling the Axinom API.
  
• Use a license token intended for different content instead of the one being played.
  
• Test simultaneous playback across multiple devices and platforms, and confirm that any access restrictions are handled gracefully.

Profile/Age Restriction Testing

Most OTT apps allow multiple profiles on a single subscription, giving users a more personalised experience with distinct preferences, watch history, and recommendations. 

Each profile can have specific settings and restrictions, such as age-based content filters, to ensure that sensitive or mature material is blocked according to the user’s age.

This testing verifies that restrictions are effective, user-friendly and compliant with regional regulations or industry standards regarding content accessibility and the protection of minors. 

This is particularly important for platforms that offer a wide range of content, including potentially sensitive or mature material that’s unsuitable for younger audiences. 

Some checkpoints when performing profile-based testing are:

• Verify that content is age-restricted based on content ratings (e.g., PG, R) and the user profile’s age.
  
• Ensure content accessibility complies with regional age regulations, for example, in Singapore, R21 content is accessible only to users aged 21+.
  
• Test parental PIN functionality for accessing higher-age profiles, and ensure updates sync across all platforms.
  
• Check that playback progress is saved by profile and can be resumed across devices.

• Verify that content added to “Favourites” or “My List” is profile-specific as well.

Geoblock and VPN Testing

Geoblock testing in OTT apps checks content access restrictions based on a user’s geographic location. This is crucial for OTT platforms that distribute content globally, as they must adhere to licensing agreements, regional regulations, and content distribution rights.

In geoblock testing, we simulate various scenarios to verify that users in different locations are denied access to unauthorised content as required. This includes:

• Validating with different IP addresses or location settings to replicate user experiences across multiple regions.
  
• Switching between regions to test content availability.
  
• Verifying that end users see a clear and graceful message explaining why content is restricted and outlining regional limitations.

VPN testing evaluates how Virtual Private Networks (VPNs) interact with an OTT platform’s content delivery and geolocation restrictions. VPNs are commonly used to bypass geographical restrictions and access content that would otherwise be blocked or restricted in a given region. 

We test whether users can access location-restricted via a VPN.

Analytics

Analytics in OTT testing involves gathering and analysing data on performance, usage patterns, errors, and user interactions across OTT platforms. Several tools can be used to track the performance of our app.

Our analytics toolkit includes partnerships with:

• Crashlytics – Tracks app crashes and stability issues in real time.

• Bugsnag – Captures errors, crashes, and in-app issues across devices.

• Mixpanel, Google Analytics – Monitors user behaviour, event flows, and engagement.

• MUX – Measures video quality, playback issues, and start-up times.

• Loggly – Logs backend performance, errors, and system-level events.

• Youbora – Provides detailed video session analytics and viewer behaviour.

• Conviva – Tracks performance during video playback, including load times and buffering.

Installation/Uninstallation/Updates

Here, we test the app to confirm that it can be installed, uninstalled, and updated correctly and smoothly. This is essential for maintaining a positive user experience and ensuring the reliability and stability of software applications throughout their lifecycle. 

Here’s what each aspect typically involves:

Take the guesswork out of OTT testing 

To stay competitive, OTT platforms regularly roll out updates, new features, and content additions. Testing must support agile development cycles, rapid app upgrades, and quick validation of new functionalities without compromising quality. 

At DIAGNAL, we achieve this by planning according to project requirements and executing the plans as closely as possible.

In conclusion, these are the essential checkpoints for testing an OTT application. 

We can include additional tests beyond those listed as per your specific requirements. OTT is a fast moving industry, and we need to identify innovative ways to test and ensure a smooth and delightful app experience for our viewers.

If you want to take the guesswork out of OTT testing, and make sure your platform is ready for anything, get in touch. We’d love to show you how we can help.