WebSocket test server migration on ExtensionApiTest.WebSocket

chrome/test/data/extensions/api_test/websocket/test.js

 // Copyright (c) 2012 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 function echoTest(port) {
-  var url =
-      "ws://localhost:" + port + "/websocket/tests/hybi/workers/resources/echo";
+  var url = "ws://localhost:" + port + "/echo";

[Ryan Sleevi, 2012/10/09 19:39:07]

nit: For some tests, we also parameterize the hostname used by the test server
(either through DNS fakery or for working around some weird winsock issues on
Windows)

A future CL would be good to considering making host and port parameterized

[Takashi Toyoshima, 2012/10/10 01:34:48]

I see.
Thank you for advice.

   var ws = new WebSocket(url);
   var MESSAGE_A = "message a";
   var MESSAGE_B = "message b";
 
   ws.onopen = function() {
     chrome.test.log("websocket opened.");
     ws.send(MESSAGE_A);
   };
 
   ws.onclose = function() {
     chrome.test.log("websocket closed.");
   }
 
   ws.onmessage = function(messageEvent) {
     chrome.test.log("message received: " + messageEvent.data);
     chrome.test.assertEq(MESSAGE_A, messageEvent.data);
 
     ws.onmessage = function(messageEvent) {
       chrome.test.log("message received: " + messageEvent.data);
       chrome.test.assertEq(MESSAGE_B, messageEvent.data);
       ws.close();
 
       chrome.test.succeed();
     };
 
     ws.send(MESSAGE_B);
   };
 }
 
-chrome.test.runTests([
-  chrome.test.getConfig(function(config) {
-    echoTest(config.testWebSocketPort);
-  })
-]);
+chrome.test.getConfig(function(config) {
+  chrome.test.runTests([
+    function runEchoTest() {
+      echoTest(config.testWebSocketPort);
+    }
+  ]);
+});
+