Basic tests for Presentation API

[taff-franck]

The following test was perform:

• PresentationRequest with incorrect url
• PresentationRequest with correct url
• reconnect() with wrong Presentation ID

[hoppipolla-critic-bot]

Critic review: https://critic.hoppipolla.co.uk/r/6548

This is an external review system which you may optionally use for the code review of your pull request.

In order to help critic track your changes, please do not make in-place history rewrites (e.g. via git rebase -i or git commit --amend) when updating this pull request.

[zqzhang]

w3c-test:mirror

[zqzhang]

Should be TypeError. See discussion at

https://critic.hoppipolla.co.uk/showcomments?review=3331&filter=all

[louaybassbouss]

@taff-franck in the Presentation API F2F Meeting we discussed also the way how we create Presentation URLs that are compatible with Google Cast Receivers and other Receiving UAs. We need to replace in all tests 'https://google.com/cast#__castAppId__=CC1AD845/__castClientId__=' + client_id; with 'http://w3c-test.org/presentation-api/receiving-ua/idlharness.html#__castAppId__=2334D33A/__castClientId__=' + client_id;. the Cast Id for http://w3c-test.org/presentation-api/receiving-ua/idlharness.html is in this case 2334D33A. This will work for now in Chrome canary https://www.google.com/chrome/browser/canary.html. Other Implementations like crosswalk from Intel will still work with this solution and the hash parameters will be ignored.

[zqzhang]

'http://w3c-test.org/presentation-api/receiving-ua/idlharness.html#__castAppId__=2334D33A/__castClientId__=' + client_id;

Can we use relative presentation URL?

[louaybassbouss]

@zqzhang agree relative URL is better if we want to run the tests from a local system and not from w3c-tests.org. @taff-franck please consider this comment.

[zqzhang]

s/SyntaxError/TypeError/g

[zqzhang]

Thanks, LGTM.