Closed jpiesing closed 11 months ago
This is raised on an HbbTV set and not to be related to the test. The test results are not affected by this.
This is raised on an HbbTV set and not to be related to the test. The test results are not affected by this.
Is it reasonable to catch this instead of generating an error in the test report? This error will be very confusing to people.
This is raised on an HbbTV set and not to be related to the test. The test results are not affected by this.
Is it reasonable to catch this instead of generating an error in the test report? This error will be very confusing to people.
It is not possible since the error is triggered by the HbbTV UA on only a TV set and not from the testing code. We know this error from the other HbbTV dev on the specific TV.
If you can't catch it, can you add it to the documentation somewhere?
The script errors cannot be caught. Needs to be documented that some implementations generate the error. @louaybassbouss Fraunhofer to document in test execution section of Deploy. @louaybassbouss
Added documentation for this (https://github.com/cta-wave/dpctf-tests/pull/141)
Fixed.
What should be done about these?
How significant are they?