Submitting Builds to Conviva

Use the Enter App Details tab in the Apps dashboard to qualify your device application.

1. Qualify Device Application

1. In the navigation menu, click Apps tab.

   The Apps dashboard appears.

2. To qualify a new device application, click New App. To resume qualification, select the device application from the list of device applications.

   If you want to delete a device application from the list of device applications, select the device application and in the Enter App Details tab, click Delete App.

3. In the Enter App Details tab, provide the device application's qualification information (device application, operating system, media player, content, streaming protocol, and ad information) accurately.

   If you are a non StreamSensor customer, you can use the Integrated with Stream Sensor field to select whether your device application is integrated with StreamSensor or not.

4. Verify the qualification information and click Next to submit the qualification request. The status changes to Under Qualification and you can now use the Integrate SDK/Library tab to download an SDK as per your requirements.

Use the Integrate SDK/Library tab in the Apps dashboard to download an SDK, and integrate your device application with Conviva sensors.

2. Integrate Device Application

1. Navigate to the Apps tab.

   The Apps dashboard appears.

2. Select the device application that requires qualification.

3. In the Integrate SDK/Library tab, choose a SDK that fits your requirements.

   

4. To download the SDK, click Download SDK.

5. To view the integration instructions for the SDK, click View Integration Details, which redirects you to the Conviva Docs. To integrate your device application with Conviva sensor, follow the instructions on the Conviva Docs for the desired platform.

   To enable faster integration with Android players, click the View Integration Details button for Android apps and install the Integration Assistant Plugin. The plugin automatically adds the SDK dependencies to your Android project and generates a ConvivaHelper.java file with all the code that is required for the integration.
   

6. After you integrate your device application with the Conviva sensor, test your integration by performing self-validation using Touchstone. To see some examples of common validation issues, watch videos available on that page.

7. To initiate the validation process for your device application, click Next.

After setting up your device application metadata in VSI Integration, use the Validate Integration tab in the Apps dashboard to submit the qualified device application to Conviva for validation. If your device application passes Conviva validation completely or with minor issues, then your device application is ready for launch. If it fails Conviva validation, then you must fix the issues and re-submit the device application for validation.

Prerequisites

• Ensure that you've created a device application, added the metadata strategy, and included the desired Conviva SDK integration.

3. Submit Device Application for Validation

1. Navigate to the Apps tab. The Apps dashboard appears.

2. Select the qualified device application that requires validation.

   • If you're submitting the build for the first time, navigate to the Validate Integration tab and click Submit for QA button.

     

   • If you've already submitted the build for validation, selecting the app from the apps list displays the previous build validation results on the right-hand section. If the previous validation failed with errors, you must fix them and resubmit for validation.

     To find more details about the errors and the steps to reproduce them, check the Notes column for the failed metrics.

     

     Fix the issues and click Submit for QA button to resubmit the build for validation.

     

3. The Review App Details dialog box appears.

   

4. Verify the device application's qualification information. To edit the information, click Edit App Details.

5. Click Next to continue.

   The Enter Build Submission Details dialog box appears.

   

6. Enter the build submission details and click Submit.

Form Fields
Add the app version number that needs testing An incorrect app version needs a new validation request to be submitted. To know the previous app versions, refer to the version history:
Select ‘Yes’ if Conviva should download and test the latest version of the production app. Select ‘No’ if it’s a staging/release-candidate build that is not the in-market production build. In the Additional Notes section: Include all information about where and how to download the build. Specify if the build requires VPN or login details to install or run. For Test Harness submitted players, provide detailed steps on how to set it up. For Test Flight submitted apps (or other distribution apps), provide access to team.devices@conviva.com for dev environment testing access. Upload the side-load build to the corresponding Brand and Platform Box Folder. If you do not have access to the Box Folders, reach out to your Conviva representative. For apps requiring UDID or Serial Number whitelisting, reach out to your Conviva representative to get this information before submitting an app.
Sample URL: https://<your-application-url> The value need not be a URL always. Enter N/A if not applicable.
Username: Enter the username to access your application URL. Enter N/A if not applicable. Password: Enter the password to access your application. Enter N/A if not applicable.
(If Yes, MVPD Type will be required) MVPD, or Multichannel Video Programming Distributor, is a service that distributes or provides multiple television channels as part of a package to which customers subscribe (e.g. Comcast, DISH, DirecTV)
Live Video and/or Video on Demand (VoD) i. If QA should test both Live and VoD, select both check boxes. ii. If QA should test one or the other only, then select either Live Video OR VoD.
Select one of the following options: Exhaustive: complete end to end comprehensive testing. Custom: metric or test case specific testing, leveraged for specific issue resolution.
Any other information the QA may need to access/configure/install the build, such as: From where and how to download the build The VPN or login credentials to install or run the build Configuration steps for Test Harness submitted players Application Device Information Target Release Dates (e.g. Formal Certification Submission, RC, Go-Live) Testing Information/Client limitations Additional Test Cases/Edge Cases

After you submit a device application for validation, Conviva validates your device application and the displays the status in the Apps dashboard. You receive an email notification when the build is certified as Validation Passed, Validation Failed, or Validation Passed with Issues.

If your device application passes the validation completely or with minor issues, then you can launch the device application. If it fails the validation, then you must fix the issues and re-submit the device application for validation.

4. Check Validation Status

1. Navigate to the Apps tab.

   The Apps dashboard appears.

2. Select the device application. The Conviva QA tab displays the validation results; Impacted Metrics, Required, and Custom metadata.

   A note is displayed at the top if at least one testcase is failed.
   
   

   Column	Description
   Impacted Metrics	This section lists the passed and failed metrics. The metric names are displayed according to the customer type. For example, Video-only customers see the metrics labeled as "VSF" (Video Start Failure), "VST" (Video Start Time), "VPF" (Video Playback Failure), and so on. Stream-only customers see the same metrics labeled as "SSF" (Stream Start Failure), "SST" (Stream Start Time), and "SPF" (Stream Playback Failure). Red triangle - If a metric is marked as under or over reported, and one or more associated test cases were marked as failed. Grey triangle - If a metric is marked as under or over reported, and the associated test case was marked as limitation. By default, this section displays all metrics. To view the impacted metrics, toggle the View All Metrics option.
   Required Metadata	This section lists the passed and failed Required metadata.
   Custom Metadata	This section lists the passed and failed Custom metadata. Identify the custom metadata type by the tag, Content or Ad, adjacent to the metadata key.
   Unexpected Metadata	This section lists the passed and failed Unexpected metadata. Identify the unexpected metadata type by the tag, Content or Ad, adjacent to the metadata key.

   

   To export the results, click Export to Pdf or Export to Excel from the Kebab icon.
   
   To refer to the integration instructions for your device platform, click the Simplified SDK: <Player Name> link that redirects you to the Conviva Docs.

3. If your validation fails, fix the issues, and click Submit for QA to re-submit the device application for validation.

5. Share the dashboard.

1. Click Share Report from the kebab menu adjacent to the Submit for QA button.

   

2. Click Copy to Clipboard in the Share Dashboard pop-up window, and share the copied link with others.