Rebuild test history databases when starting up performance_ui_tests.

[In this reland, manually load the browser dll as a resource on Windows.]

Previously, whenever the theme or history database format were modified, a
large binary database or pak file had to be committed. This was only done
intermittently, messing up some perf expectations. Since last June, this
has added over 100 megabytes to our repository weight.

By generating the SQLite databases and Cached Theme.pak files at startup
of the one test suite that uses them, we're guaranteed that we'll always
be using the current versions and won't add upgrade costs to our
performance_ui_tests. We'll also not continuously add to new binary
resources to the permanent git archive.

BUG=111570
TBR=sky@chromium.org

First Review: https://codereview.chromium.org/14273023

Review URL: https://codereview.chromium.org/14585015

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

1 files changed, 0 insertions, 13 deletions

diff --git a/chrome/test/ui/ui_test.h b/chrome/test/ui/ui_test.h
index 1ce731b..02d759a 100644
--- a/chrome/test/ui/ui_test.h
+++ b/chrome/test/ui/ui_test.h
@@ -45,12 +45,6 @@ class FilePath;
 // rather than UITestBase.
 class UITestBase {
  public:
-  // Profile theme type choices.
-  enum ProfileType {
-    DEFAULT_THEME = 0,
-    COMPLEX_THEME = 1,
-  };
-
   // ********* Utility functions *********
 
   // Launches the browser only.
@@ -148,10 +142,6 @@ class UITestBase {
   // Gets the executable file path of the Chrome browser process.
   const base::FilePath::CharType* GetExecutablePath();
 
-  // Returns the directory name where the "typical" user data is that we use
-  // for testing.
-  static base::FilePath ComputeTypicalUserDataSource(ProfileType profile_type);
-
   // Return the user data directory being used by the browser instance in
   // UITest::SetUp().
   base::FilePath user_data_dir() const {
@@ -328,9 +318,6 @@ class UITestBase {
   // Launches browser and AutomationProxy.
   scoped_ptr<ProxyLauncher> launcher_;
 
-  // Are we using a profile with a complex theme?
-  ProfileType profile_type_;
-
   // PID file for websocket server.
   base::FilePath websocket_pid_file_;