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
diff --git a/chrome/browser/search_engines/template_url_unittest.cc b/chrome/browser/search_engines/template_url_unittest.cc
index 922ccb65..eabe0780 100644
--- a/chrome/browser/search_engines/template_url_unittest.cc
+++ b/chrome/browser/search_engines/template_url_unittest.cc
@@ -9,7 +9,6 @@
#include "chrome/browser/rlz/rlz.h"
#include "chrome/browser/search_engines/search_terms_data.h"
#include "chrome/browser/search_engines/template_url.h"
-#include "chrome/test/base/testing_browser_process_test.h"
#include "testing/gtest/include/gtest/gtest.h"
// Simple implementation of SearchTermsData.
@@ -40,7 +39,7 @@
DISALLOW_COPY_AND_ASSIGN(TestSearchTermsData);
};
-class TemplateURLTest : public TestingBrowserProcessTest {
+class TemplateURLTest : public testing::Test {
public:
virtual void TearDown() {
TemplateURLRef::SetGoogleBaseURL(NULL);
