WebSocket test server migration on ExtensionApiTest.WebSocket

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

Index: chrome/test/data/extensions/api_test/websocket/test.js
diff --git a/chrome/test/data/extensions/api_test/websocket/test.js b/chrome/test/data/extensions/api_test/websocket/test.js
index 8041593cb39cadfdf601c3af45b2eec7a0ec2813..2e2adca09901a93bd2d08c115ddb3723e2d4a278 100644
--- a/chrome/test/data/extensions/api_test/websocket/test.js
+++ b/chrome/test/data/extensions/api_test/websocket/test.js
@@ -3,8 +3,7 @@
 // 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";
@@ -34,8 +33,11 @@ function echoTest(port) {
   };
 }
 
-chrome.test.runTests([
-  chrome.test.getConfig(function(config) {
-    echoTest(config.testWebSocketPort);
-  })
-]);
+chrome.test.getConfig(function(config) {
+  chrome.test.runTests([
+    function runEchoTest() {
+      echoTest(config.testWebSocketPort);
+    }
+  ]);
+});
+