Support automatic javascript test registry in gtest when creating WebUI tests.

chrome/browser/ui/webui/web_ui_browsertest.cc

 // Copyright (c) 2011 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.
 #include "chrome/browser/ui/webui/web_ui_browsertest.h"
 
 #include <string>
 #include <vector>
 
 #include "base/path_service.h"
 #include "base/utf_string_conversions.h"
@@ skipping 186 matching lines @@
   AddLibrary(FilePath(FILE_PATH_LITERAL("sample_downloads.js")));
 
   // Navigate to UI.
   // TODO(dtseng): make accessor for subclasses to return?
   ui_test_utils::NavigateToURL(browser(), GURL(chrome::kChromeUIDownloadsURL));
 
   ASSERT_TRUE(RunJavascriptTest("testAssertFalse"));
   ASSERT_TRUE(RunJavascriptTest("testInitialFocus"));
   ASSERT_FALSE(RunJavascriptTest("testConsoleError"));
 }
+
+// This test framework is used in the generated tests, which are included below.
+class WebUIBrowserTestPass : public WebUIBrowserTest {
+ private:
+  // Because the inline file will be generated to call the javascript methods
+  // via RunJavascriptTest, we need to do any preliminary setup in this method.
+  // Note: WebUIBrowserTest doesn't override setup, so no need to call its
+  // SetupOnMainThread().
+  virtual void SetUpOnMainThread() OVERRIDE {
+    ui_test_utils::NavigateToURL(browser(),
+                                 GURL(chrome::kChromeUIDownloadsURL));

[Paweł Hajdan Jr., 2011/06/15 08:12:31]

The comments don't explain why we're navigating to the downloads page.

[Sheridan Rawlins, 2011/06/15 23:54:32]

Ok, I made a dummy page and navigate to there instead of using downloads page.

On 2011/06/15 08:12:31, Paweł Hajdan Jr. wrote:

+  }
+};
+
+#include "chrome/browser/ui/webui/web_ui_browsertest-inl.h"