Scrape search definitions from forms that have onsubmit handlers. The scraping is done after submit events are handled by the page DOM so doing this is safe.

Adds test infrastructure for determining that scraping occurs on submit:
- allow testserver to be configured to serve pages from / on the server
- provide a ui test util that navigates and waits for N subsequent redirections/navigations before returning control to the test to handle automated submission

Eric, please review the test server changes.
Scott, please look over everything else.
Review URL: http://codereview.chromium.org/62145

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@13444 0039d316-1c4b-4281-b951-d872f2087c98

1 files changed, 8 insertions, 0 deletions

diff --git a/chrome/test/in_process_browser_test.h b/chrome/test/in_process_browser_test.h
index 89de9b9..457516e 100644
--- a/chrome/test/in_process_browser_test.h
+++ b/chrome/test/in_process_browser_test.h
@@ -12,6 +12,9 @@
 
 class Browser;
 class Profile;
+namespace net {
+class RuleBasedHostMapper;
+}
 
 // Base class for tests wanting to bring up a browser in the unit test process.
 // Writing tests with InProcessBrowserTest is slightly different than that of
@@ -64,6 +67,11 @@ class InProcessBrowserTest : public testing::Test, public NotificationObserver {
   // Override this rather than TestBody.
   virtual void RunTestOnMainThread() = 0;
 
+  // Allows subclasses to configure the host mapper. By default this blocks
+  // requests to google.com as Chrome pings that on startup and we don't want to
+  // do that during testing.
+  virtual void ConfigureHostMapper(net::RuleBasedHostMapper* host_mapper);
+
   // Starts an HTTP server.
   HTTPTestServer* StartHTTPServer();