WebSocket test server migration on ExtensionApiTest.WebSocket

chrome/browser/extensions/extension_apitest.h

 // 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.
 
 #ifndef CHROME_BROWSER_EXTENSIONS_EXTENSION_APITEST_H_
 #define CHROME_BROWSER_EXTENSIONS_EXTENSION_APITEST_H_
 
 #include <deque>
 #include <string>
 
 #include "base/compiler_specific.h"
 #include "base/values.h"
 #include "chrome/browser/extensions/extension_browsertest.h"
 #include "content/public/browser/notification_registrar.h"
 
 class FilePath;
 
-namespace content {
-class TestWebSocketServer;
-}
-
 namespace extensions {
 class Extension;
 }
 
 
 // The general flow of these API tests should work like this:
 // (1) Setup initial browser state (e.g. create some bookmarks for the
 //     bookmark test)
 // (2) Call ASSERT_TRUE(RunExtensionTest(name));
 // (3) In your extension code, run your test and call chrome.test.pass or
@@ skipping 145 matching lines @@
  private:
   bool RunExtensionTestImpl(const char* extension_name,
                             const std::string& test_page,
                             int flags);
 
   // Hold details of the test, set in C++, which can be accessed by
   // javascript using chrome.test.getConfig().
   scoped_ptr<DictionaryValue> test_config_;
 
   // Hold the test WebSocket server.
-  scoped_ptr<content::TestWebSocketServer> websocket_server_;
+  scoped_ptr<net::TestServer> websocket_server_;
 };
 
 // PlatformAppApiTest sets up the command-line flags necessary for platform
 // apps (if any).
 class PlatformAppApiTest : public ExtensionApiTest {
  public:
   PlatformAppApiTest();
   virtual ~PlatformAppApiTest();
 
   virtual void SetUpCommandLine(CommandLine* command_line) OVERRIDE;
 };
 
 #endif  // CHROME_BROWSER_EXTENSIONS_EXTENSION_APITEST_H_