Switch ChromeTestSuite to the same convention as ContentTestSuite:

the test suite implicitly provides global resources for each test,
but they're re-initialized between each test.

The performance overhead is negligible.

We need that to continue moving tests from unit_tests
to content_unittests. Because of shared test fixtures
the test suites need to be compatible.

BUG=90443

Review URL: http://codereview.chromium.org/7744039

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

1 files changed, 1 insertions, 2 deletions

diff --git a/chrome/browser/autofill/autofill_download_unittest.cc b/chrome/browser/autofill/autofill_download_unittest.cc
index 58ea787..3b6f1ac 100644
--- a/chrome/browser/autofill/autofill_download_unittest.cc
+++ b/chrome/browser/autofill/autofill_download_unittest.cc
@@ -14,7 +14,6 @@
 #include "chrome/browser/autofill/form_structure.h"
 #include "chrome/test/base/test_url_request_context_getter.h"
 #include "chrome/test/base/testing_browser_process.h"
-#include "chrome/test/base/testing_browser_process_test.h"
 #include "chrome/test/base/testing_profile.h"
 #include "content/test/test_url_fetcher_factory.h"
 #include "net/url_request/url_request_status.h"
@@ -115,7 +114,7 @@ class AutofillDownloadTestHelper : public AutofillDownloadManager::Observer {
   scoped_refptr<net::URLRequestContextGetter> request_context_getter;
 };
 
-typedef TestingBrowserProcessTest AutofillDownloadTest;
+typedef testing::Test AutofillDownloadTest;
 
 TEST_F(AutofillDownloadTest, QueryAndUploadTest) {
   MessageLoopForUI message_loop;