RE: Adding WebSocket and WebWorker test suites to testing framework

That would be fine from my view - though the SSL cert has expired on the Jetty server.
Mike can you get this fixed?

Without this the secure test fail.
Once this gets fixed I want to have a CFC to get all the web socket tests approved (ms2ger and Microsoft tests) since they have been updated to match the spec changes (unpaired surrogate and arraybufferview).

-Kris

-----Original Message-----
From: Arthur Barstow [mailto:art.barstow@nokia.com] 
Sent: Wednesday, October 17, 2012 6:44 AM
To: Kris Krueger; Simon Pieters; public-webapps-testsuite@w3.org; Ms2ger @ Mozilla
Subject: Adding WebSocket and WebWorker test suites to testing framework

Hi All,

To facilitate automated running of the WebSocket and WebWorker tests, what do you think about adding them to the test framework now(ish):

    <http://w3c-test.org/framework/app/suite>

It appears there is a precedence to include various submissions as separate entries in the framework. For instance, there are currently three entries for IndexedDB: Microsoft, Ms2ger and Opera.

Should all of the submissions be added to the framework separately i.e. 
Workers/Microsoft, Workers/Opera, WebSockets/Microsoft and WebSockets/Ms2ger or should there first be some type of approval step first, such that there is a single entry for Workers and a single entry for WebSocket?

Simon - FYI, PLH just reported (in #testing channel) Opera's Workers tests jsframework.js (instead of testharness.js).

-Thanks, AB

Received on Friday, 19 October 2012 17:51:44 UTC