Produce a preliminary implementation report about remote-playback

[mounirlamouri]

I've sent a PR to update the README. The tests in the repo are the ones avayvod@ and I uploaded from Blink. I wouldn't say I'm happy because a lot of tests require to interact with the remote device and we can't do that from WPT but it's better than nothing.

[Honry]

@avayvod, @mounirlamouri, please tell me if anything I can help. :)

[anssiko]

@mounirlamouri if you'd like @Honry to take a stab at the implementation report, he'd appreciate instructions on how to setup the test environment. @Honry has developed manual tests for other APIs such as battery-status in the past.

[mounirlamouri]

I guess something you can start with is looking at the tests that we have in Blink using our internal test infrastructure.

The issue with this API is that you will have to use a Chrome Cast compatible device to test the API on Chrome but another browser might not support Chrome Cast. The test preconditions will have to start with something a bit hand-wavy like "Have a device compatible with the browser on your WiFi". Because only Chrome (maybe other Chrome-based browsers) has an implementation for this at the moment, it would be hard to be clearer.

[Honry]

@mounirlamouri, I glance over both Chromium Layout tests and wpt tests, almost all the tests are about exceptions and I can easily generate the test report. If you need please tell me which platforms should be covered.

The issue with this API is that you will have to use a Chrome Cast compatible device to test the API on Chrome but another browser might not support Chrome Cast.

This is the issue Presentation API had ever encountered, but now they have much more sufficient test suite, maybe we can consult them.

[mounirlamouri]

At the moment, only Chrome Android supports the Remote Playback API so I guess you should only do a report on this platform?

Following a pattern similar to Presentation API would make sense. I wonder how much we can use this as an inspiration as the Remote Playback API is fairly simpler.

[avayvod]

Chrome Desktop also exposes the API but doesn't support any remote playback devices yet.

[Honry]

Actually the test result of current test suite are all pass on both Chrome for Android and Desktop, I just committed the report at w3c/test-results#102. PTAL.

[Honry]

Following a pattern similar to Presentation API would make sense. I wonder how much we can use this as an inspiration as the Remote Playback API is fairly simpler.

@mounirlamouri, let's talk about the issue in this thread: #92