W3C home > Mailing lists > Public > public-secondscreen@w3.org > November 2017

Re: [remote-playback] Remote Playback API test automation

From: Louay Bassbouss via GitHub <sysbot+gh@w3.org>
Date: Thu, 02 Nov 2017 08:20:33 +0000
To: public-secondscreen@w3.org
Message-ID: <issue_comment.created-341348447-1509610832-sysbot+gh@w3.org>
@Honry `<video>.remote.test.deviceAvailable = true` is enough for [Observing remote playback device availability][1] but I am not sure how to test the [RemotePlayback Connection State][2]. We may need a 'FakePlaybackScreen' similar to this [proposal][3] from @mfoltzgoogle. The 'FakePlaybackScreen' can have some additional attributes like `playing`, `paused`, etc. to test the transition between the different remote playback connection states. What do you think?

[1]: https://www.w3.org/TR/remote-playback/#observing-remote-playback-device-availability
[2]: https://www.w3.org/TR/remote-playback/#the-state-attribute
[3]: https://github.com/mfoltzgoogle/presentation-test-api/blob/master/presentation_test_api.md

-- 
GitHub Notification of comment by louaybassbouss
Please view or discuss this issue at https://github.com/w3c/remote-playback/issues/92#issuecomment-341348447 using your GitHub account
Received on Thursday, 2 November 2017 08:20:35 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:19:03 UTC