- From: Hans-Helge Buerger <web-platform-tests-notifications@w3.org>
- Date: Fri, 25 Nov 2016 10:11:04 GMT
- To: public-web-platform-tests-notifications@w3.org
That is all still very confusing to me 🤔 ### Why did I change `common.js`? I tested `var request = new PresentationRequest(presentationUrls);` with different URLs and the array from `common.js`. My tests always fail when I use the predefined URLs or array with: "NotFoundError: No screens found.". However if I change the google cast URL so it holds a `castClientId` it seems to work. And if I give an array where this changed google cast URLs is on index 0 it works as well. Using `support/presentation.html` does not work for me. ### 1. Browser Implementation So if browsers don't support an array as constructor param, why do we use them in `common.js`? I mean, how can I make sure my test is correct if I write one which I cannot verify? I do understand, that browser should implement the specs and the test should cover the spec not the current browser implementation. But the question remains: How can I make sure the test is correct? > Both points mean that most tests currently fail in practice, but I don't think that is a bug with the test suite. This makes it hard to author tests for sure. I'll give it a try with a true Cast receiving app to see if we can ease our lives while implementations catch up. Ok, you test it with a _true_ Cast app. Can I also test it with a _true_ app? View on GitHub: https://github.com/w3c/web-platform-tests/pull/4222#issuecomment-262923273
Received on Friday, 25 November 2016 10:11:18 UTC