Getting started with "WAVE Streaming Media Test Suite - Devices"

Linux system is highly recommended for this guide, use other systems at your own risk.

There are three phases:

1. Deployment (one time action, to be performed by IT personnel)
   • Host machine requirements
   • Clone repository
   • Build the image and download content
   • Configure access to the test runner
     • With IP address
     • With domain
   • Agree to the EULA
   • Start the test runner
2. Test execution and recording (to be performed by tester)
3. Observation (analysis of recording to be performed by tester or other person)
   • Clone repository
   • Build the image
   • Configure the Observation Framework
   • Running the analysis
   • Getting the analysis results
   • Debugging

Phase 1: Deployment of the test runner (one time action, to be performed by IT personnel)

Host machine requirements

• on Linux (applies also for macOS and Windows with WSL2):
  • docker
  • docker-compose
  • git
• on Windows (without WSL2):
  • Docker-Desktop
    • To access docker the user requires admin permissions (or a special configuration which is out of scope for this guide)
  • git
  • Windows Terminal (For running commands)
• TLS server certificate for a domain that can be resolved by the device under test (we use yourhost.domain.tld for the domain) Note: While some tests can be run without this, valid certificates are needed for tests of EME and encrypted content.
• camera that records at 120 fps or more (AVC/h.264)

Note: The test suite has been installed and run on other host machines with varying degrees of success. On Windows, it has been used with the free version of docker running in WSL2. It has been used on a Mac. No support or assistance is available for either of these or anything else similar. Neither of these should be attempted unless you know what you are doing or have access to someone who does. It is critical to ensure that the test runner can be contacted from the device under test and from the observation framework. This may be problematic with some combinations of virtualization technologies and network configurations.

Device under test requirements

The device under test ("DUT") needs at least one mechanism for showing an arbitrary URL in the browser to be tested. These mechanisms may be standard (e.g. including the URL in a broadcast signal) or private / proprietary. Note: If the DUT supports HbbTV then one possibility is to build an MPEG-2 transport stream containing the URL. One resource that may help with this specific case is https://github.com/ebu/hbbtv-dvbstream .

Clone repository

Using the git command line tool, you can download the current version of the dpctf-deploy repository to your system:

Linux / macOS / WSL2:

git clone https://github.com/cta-wave/dpctf-deploy

Windows:

git clone https://github.com/cta-wave/dpctf-deploy

Now all files necessary to setup the test runner are located in the dpctf-deploy directory. All following actions will be performed in here.

Build the image and download content

To build the image run the build script in the dpctf-deploy directoy:

Linux / macOS / WSL2:

./build.sh

Windows:

.\build.bat

Download test content to serve locally (note: this pulls a lot of data and may take a while):

Linux / macOS / WSL2:

./import.sh

Windows:

.\import.bat

Configure access to the test runner

The test runner can be configured to be accessed by either an IP or a domain. Setting up the access with an IP address is a lot easier than with domain, however, https tests only work with a valid certificate on TVs. It is recommended to only use IP address access for debugging the setup.

With IP address

Note: When using an IP address https tests won't work.

In the dpctf-deploy directory open config.json and enter your host IP address in the host_override field:

dpctf-deploy/config.json

{
  "browser_host": "web-platform.test",
  "alternate_hosts": {
    "alt": "not.web-platform.test"
  },
  "wave": {
    "aliases": [],
    ....
    "api_titles": [],
    "host_override": "172.152.15.3"

With domain

In the dpctf-deploy directory open config.json and enter your host domain or IP address in the host_override field

dpctf-deploy/config.json

{
  "browser_host": "web-platform.test",
  "alternate_hosts": {
    "alt": "not.web-platform.test"
  },
  "wave": {
    "aliases": [],
    ....
    "api_titles": [],
    "host_override": "yourhost.domain.tld"

Some tests require a DNS entry and valid certificates to execute correctly. For this please copy the domain's certificate into the certs directory. Finally, the certificates must be configured by adding following at same level as "wave" field, note that the key and pem files must be named according to your needs:

Running https tests requires a valid certificate for your domain. Copy your certificates files into the certs directory inside the dpctf-deploy directory:

dpctf-deploy/certs

cacert.pem
private.key
certificate.pem

Then copy the following configuration to the root of config.json

  "ssl": {
    "type": "pregenerated",
    "encrypt_after_connect": false,
    "openssl": {
      "openssl_binary": "openssl",
      "base_path": "_certs",
      "force_regenerate": false,
      "base_conf_path": null
    },
    "pregenerated": {
      "ca_cert_path": "./certs/cacert.pem",
      "host_key_path": "./certs/private.key",
      "host_cert_path": "./certs/certificate.pem"
    },
    "none": {}
  },

Where ca_cert_path, host_key_path and host_cert_path have the correct file names of your certificate.

Your config.json should look something like this:

dpctf-deploy/config.json

{
  "browser_host": "web-platform.test",
  "alternate_hosts": {
    "alt": "not.web-platform.test"
  },
  "ssl": {
    "type": "pregenerated",
    "encrypt_after_connect": false,
    "openssl": {
      "openssl_binary": "openssl",
      "base_path": "_certs",
      "force_regenerate": false,
      "base_conf_path": null
    },
    "pregenerated": {
      "ca_cert_path": "./certs/cacert.pem",
      "host_key_path": "./certs/private.key",
      "host_cert_path": "./certs/certificate.pem"
    },
    "none": {}
  },
  "wave": {
    "aliases": [],
    "results": "./results",
    "timeouts": {
        "automatic": 100000,
        "manual": 100000
    },
    "enable_results_import": false,
    "web_root": "/_wave",
    "persisting_interval": 20,
    "api_titles": [],
    "host_override": "yourhost.domain.tld"
  }
}

Agree to the EULA

For the test runner to start you are required to agree to the EULA.

Set AGREE_EULA to yes:

dpctf-deploy/docker-compose.yml

    environment:
      AGREE_EULA: "yes"

Start the test runner

To start the test runner, change into the dpctf-deploy directory and run:

Linux / macOS / WSL2:

docker-compose up

Windows:

docker-compose up

Wait until all http and https are started. The output should like something like this:

dpctf  | INFO:web-platform-tests:Starting https server on web-platform.test:*
dpctf  | INFO:web-platform-tests:Starting http server on web-platform.test:*

You are now able to open up the landing page of the test runner in your web browser:

http://yourhost.domain.tld:8000/_wave/index.html

or

http://<ip>:8000/_wave/index.html

If the command terminates or you see an error like the following, something went wrong with the startup:

dpctf exited with code 1

Phase 2: Test execution and recording (to be performed by tester)

To execute tests, open the landing page on the DUT using the following URL:

http://yourhost.domain.tld:8000/_wave/index.html

or if you have provided valid certificates

https://yourhost.domain.tld:8443/_wave/index.html

The tester must execute following steps

1. position video recording device (e.g. smartphone with 120fps using AVC codec) in front of the display of DUT Note: Significant care is needed. Please see documentation for obtaining recordings.

2. Either use a phone to scan the QR-Code -> test runner companion screen will open in phones's Web browser or Note the first 8 characters of the token from the landing page. Using a web browser (e.g. on the test runner PC), go to http://yourhost.domain.tld:8000/_wave/configuration.html and enter those 8 characters in the "Session token" box.

3. select the tests to be executed on DUT from provided lists Note: A good place to start for first time users would be to deselect all test groups by using the "None" button and then select one simple test, e.g. by expanding either cfhd_12.5_25_50-local or cfhd_15_30_60-local and then selecting just the sequential track playback test with stream t1 as shown.

4. start recording on recording device

5. press "Start session" button -> the test(s) should start to execute on DUT

6. once "Session completed" screen is visible on DUT then stop the recording

7. save link to testing session including the session token for later reference and report

Phase 3: Analyse recording using device observation framework

The Observation Framework analyzes the video file recorded in phase 2 and automatically adds the results to the existing results of the corresponding session. Just like the Test Runner, the Observation Framework is setup in a docker container.

Clone repository

Using the git command line tool, you can download the current version of the dpctf-deploy repository to your system:

Linux / macOS / WSL2:

git clone https://github.com/cta-wave/dpctf-deploy

Windows:

git clone https://github.com/cta-wave/dpctf-deploy

Now all files necessary to setup the test runner are located in the dpctf-deploy directory. All following actions will be performed in here.

Build the image

To build the image run the build script in the dpctf-deploy directoy:

Linux / macOS / WSL2:

./build-dof.sh

Windows:

.\build-dof.bat

Configure the Observation Framework

To configure the Observation Framework create the observation-config.ini in the cloned repositories directory. The current default config file is located in the Observation Framework's repository

To allow the Observation Framework to add the results to the Test Runner's session set the correct domain name of the Test Runner in the config file:

dpctf-deploy/observation-config.ini

test_runner_url = http://yourhost.domain.tld

Running the analysis

Run the analysis by executing the analyse-recording script:

Linux / macOS / WSL2:

./analyse-recording.sh <mp4-filepath> <options>

Windows:

.\analyse-recording.bat <mp4-filepath> <options>

For additional options please refer the the documentation

Getting the analysis results

If configured correctly in the step Configure the Observation Framework, the results of the analysis are now available in the Test Runner's session:

http://yourhost.domain.tld:8000/_wave/results.html?token=SESSIONTOKEN

The results are also located in the dpctf-deploy/observation-results directory.

Debugging

If the observation framework reports errors and/or that the device has failed, some information on analysis and debugging can be found at https://github.com/cta-wave/device-observation-framework/wiki/Debugging-Observation-Failures