- From: Louay Bassbouss via GitHub <sysbot+gh@w3.org>
- Date: Fri, 13 Oct 2017 07:54:58 +0000
- To: public-secondscreen@w3.org
@Honry sorry I missed your request from 21 Jun thanks for the reminder. Yes the setup for testing the Presentation API and RemotePlayback API Tests on Chromecast should be similar. I would say that the tests of RemotePlayback API are easier to implement since you will not deal with different Presentation URLs as in the Presentation API (You can have a look in [[1][1]] where two different Presentation URLs are specified, one for cast receivers and one for other receivers that can render a web page). In RemotePlayback API you don't need to pass any URL which makes a lot of things easier. To test on Chromecast (or any other cast receiver like Android TV) you need just to make sure that your PC and the Receiver devices are in the same Network. But you need to keep in mind when you are writing the tests to not use any code that is specific for chromecast or any specific technology, but only according the API specification. To create a test report of RemotePlayback API e.g. for Chrome Browser, the tester (for example the person who is responsible to create the report) must have the information about which receiver devices are supported by the Browser under test. The tester musst also ensure that a receiver device is available during the test. I would recommend to habe a look to the tests of Presentation API in [[2][2]] and the current Test Report in [[3][3]]. PS: when you are writing tests please keep in mind that you are testing the API Implementation and NOT the underlying protocols. [1]: https://github.com/w3c/web-platform-tests/blob/master/presentation-api/controlling-ua/common.js [2]: https://github.com/w3c/web-platform-tests/tree/master/presentation-api/controlling-ua [3]: http://w3c.github.io/test-results/presentation-api/controlling-ua/all.html -- GitHub Notification of comment by louaybassbouss Please view or discuss this issue at https://github.com/w3c/remote-playback/issues/92#issuecomment-336378718 using your GitHub account
Received on Friday, 13 October 2017 07:54:47 UTC