- From: Arthur Barstow <art.barstow@nokia.com>
- Date: Tue, 19 Feb 2013 13:42:12 -0500
- To: ext Kris Krueger <krisk@microsoft.com>
- CC: "public-webapps-testsuite@w3.org" <public-webapps-testsuite@w3.org>
On 2/14/13 12:37 PM, ext Kris Krueger wrote: > In Dec James/Simon said that they had submitted all of Opera's WebSocket tests though some sill needed to be converted. > James/Simon have you done any more converting of Opera's WebSocket tests to use testharness.js? > > I think it's quite reasonable to expect to have all the tests approved/review before the next F2F so that the spec can move forward. > James/Simon said they are 'OK' with someone converting the remaining Opera tests as well. Do you consider the tests approved by the group four months ago is sufficient to determine the CR exit criteria <http://www.w3.org/TR/websockets/#crec>? -Thanks, Art > > -Thx > > -----Original Message----- > From: Arthur Barstow [mailto:art.barstow@nokia.com] > Sent: Friday, January 11, 2013 5:02 AM > To: public-webapps-testsuite@w3.org; Kris Krueger > Subject: [websocket-test] What's the plan for reviewing and approving Opera's WebSocket tests? > > Hi Kris, All, > > Last October, WebApps' test group approved WebSocket tests submitted by Microsoft and Ms2ger [1]. Since then, Opera submitted some WebSocket tests [2]. > > What is the plan to get review and approval of Opera's tests? > > Before formal CR testing is started, alltests used for CR testing should be approved by the entire WG- not just the test group. As such, should Opera's tests first be reviewed by the test group and then the entireWG reviews the aggregate? Or, should we skip the test group's review of Opera's tests and ask the entire WG to review Opera's tests plus the tests already approved by the test group? > > -Thanks, AB > > [1] > http://lists.w3.org/Archives/Public/public-webapps-testsuite/2012Oct/0007.html > [2] http://w3c-test.org/webapps/WebSockets/tests/submissions/Opera/ > >
Received on Tuesday, 19 February 2013 18:42:44 UTC