You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If we want HbbTV implementers to try out the DPCTF test suite then we need a TS which runs the test runner - which is what #1 was about. That issue was deferred in November last year but, if we want les skilled people to be able to run the tests then this is essential.
It's a little more complex than the WMAS test runner as the TS there points to a cloud server whereas this TS would need to point to the local server where the test runner was installed. Hence the TS would need to be patched with that IP address.
We cannot assume HbbTV implementations have direct URL entry and the skill level required to use something like tsduck to make your own TS excludes a whole set of HbbTV test engineers.
The text was updated successfully, but these errors were encountered:
@jpiesing how about building a TS with http://web-platform.test:8000/_wave/index.html . The build-in DNS server is able to resolve the IP of the domain web-platform.test. For this, it is needed to the enter the DNS IP on the DUT. wdyt?
Don't we need to use the DNS IP (or something more complex) on the test runner anyway for the encrypted content tests that use EME and hence need to be run using https?
There's been a number of discussions about a TS to launch the DPCTF test runner on an HbbTV TV set.
#1
cta-wave/WMAS#61
cta-wave/WMAS#62
The TS that was created on https://github.com/cta-wave/WMAS/wiki/HbbTV is only for WMAS.
I cannot find a TS for DPCTF.
If we want HbbTV implementers to try out the DPCTF test suite then we need a TS which runs the test runner - which is what
#1 was about. That issue was deferred in November last year but, if we want les skilled people to be able to run the tests then this is essential.
It's a little more complex than the WMAS test runner as the TS there points to a cloud server whereas this TS would need to point to the local server where the test runner was installed. Hence the TS would need to be patched with that IP address.
We cannot assume HbbTV implementations have direct URL entry and the skill level required to use something like tsduck to make your own TS excludes a whole set of HbbTV test engineers.
The text was updated successfully, but these errors were encountered: