GTTF: Use a fresh TestingBrowserProcess for each test, part #4

chrome/browser/sync/glue/theme_data_type_controller_unittest.cc

Index: chrome/browser/sync/glue/theme_data_type_controller_unittest.cc
diff --git a/chrome/browser/sync/glue/theme_data_type_controller_unittest.cc b/chrome/browser/sync/glue/theme_data_type_controller_unittest.cc
index 80b6b81d7e63ac4c51f29776f714e5635caef37a..30b9bebf3aa4be8125f283b73c5d8d3a8da34e45 100644
--- a/chrome/browser/sync/glue/theme_data_type_controller_unittest.cc
+++ b/chrome/browser/sync/glue/theme_data_type_controller_unittest.cc
@@ -14,6 +14,7 @@
 #include "chrome/browser/sync/profile_sync_factory_mock.h"
 #include "chrome/browser/sync/profile_sync_service_mock.h"
 #include "chrome/test/base/profile_mock.h"
+#include "chrome/test/testing_browser_process_test.h"
 #include "content/browser/browser_thread.h"
 
 using browser_sync::ThemeDataTypeController;
@@ -32,7 +33,7 @@ class StartCallback {
     const tracked_objects::Location& location));
 };
 
-class ThemeDataTypeControllerTest : public testing::Test {
+class ThemeDataTypeControllerTest : public TestingBrowserProcessTest {
  public:
   ThemeDataTypeControllerTest()
       : ui_thread_(BrowserThread::UI, &message_loop_) {}