Testing overview

Use DVM Sandbox to validate your API integration and subscription flows before production launch. Testing starts with Bango test Partners so you can prove your integration independently. You can then test the intended Reseller-to-Content Provider partnership end to end before progressing through any production and pilot testing agreed for the launch.

Testing stages

DVM testing and launch validation typically progresses through four stages. The first two stages use Sandbox.

Two-party self-certification

Two-party self-certification lets you validate your own DVM integration before the intended counterparty needs to participate. DVM Sandbox includes Bango test Partners that act as the other side of the subscription flow: This isolates your integration from the intended live counterparty and lets you verify API requests, lifecycle handling, notifications, and operating flows. Bango provides the certification use cases required for your integration and may also provide a Postman collection to help execute them. Complete the required cases and share the results with Bango for review.

Three-party Sandbox testing

After each Partner integration works with its DVM test counterparty, test the intended partnership end to end in Sandbox. In three-party testing:

1. The intended Reseller is configured in DVM Sandbox.
2. The intended Content Provider is configured in DVM Sandbox.
3. DVM routes the configured Offer and Entitlement flows between both Partners.
4. Both Partners execute the agreed end-to-end scenarios and verify the lifecycle and operational results.

Some scenarios require the Content Provider to initiate an action, such as a Content Provider-initiated termination. Three-party testing validates the complete partnership integration before production configuration and launch.

Production testing

When the production route and configuration are ready, Bango will confirm the production testing required for the launch. Production testing validates that the production configuration behaves as expected with the intended Partners and production systems. The exact scope depends on the integration and the actions that can safely be performed before launch.

Pilot testing

Where a pilot is part of the launch plan, a controlled group uses the production integration before public release. Pilot testing focuses on the real end-to-end consumer experience, including devices, browsers, activation journeys, and operational support behavior that may not be fully represented during scripted integration testing. Bango will agree whether pilot testing is required and the associated entry and exit criteria for the launch.

What to test

Test the flows your partnership will depend on in production. For a typical subscription bundle partnership, this includes:

• Authenticate and integrate with the DVM APIs
• Discover the Products and Offers available to you
• Create a Consumer Offer
• Confirm the related Entitlement is provisioned
• Complete activation where the Product requires it
• Retrieve and handle Consumer Offer and Entitlement lifecycle states
• Suspend and resume where supported by the integration
• Cancel or terminate the Consumer Offer as required
• Receive and process applicable notifications
• Verify the resulting activity in DVM

Use the DVM API documentation for the API operations and the task guides for the behavior you are testing.

Test services and response scenarios

Use the testing mechanism that matches what you need to prove: Mock response headers use X-Magic-Number on Reseller-to-DVM Entitlement API requests. They are not supported as a general testing mechanism across other DVM APIs.

Verify your results

Validate each test from the perspective of both the API integration and the resulting DVM state.

Sandbox limitations

Sandbox is designed for functional, integration, and certification testing. Use it to validate:

• API integration behavior
• Offer and Entitlement lifecycle flows
• Reseller and Content Provider interactions
• Consumer journeys
• Operational behavior in Dashboard and Care

Sandbox uses test configuration and test data in a dedicated environment. It does not affect production consumers or production launches.

Move toward production

Complete the required self-certification and three-party testing, then share the agreed test evidence with Bango. Bango reviews the required certification results before authorizing the integration to progress to production. Production and pilot testing are then completed where required by the launch plan.