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

For a detailed description see part #1, http://codereview.chromium.org/6478005/

BUG=61062
TEST=unit_tests, possibly more

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

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

1 files changed, 2 insertions, 1 deletions

diff --git a/chrome/browser/printing/print_dialog_cloud_unittest.cc b/chrome/browser/printing/print_dialog_cloud_unittest.cc
index 6c50f1e..d2083c6 100644
--- a/chrome/browser/printing/print_dialog_cloud_unittest.cc
+++ b/chrome/browser/printing/print_dialog_cloud_unittest.cc
@@ -19,6 +19,7 @@
 #include "chrome/common/chrome_paths.h"
 #include "chrome/common/url_constants.h"
 #include "chrome/test/base/testing_profile.h"
+#include "chrome/test/testing_browser_process_test.h"
 #include "content/browser/browser_thread.h"
 #include "content/common/content_notification_types.h"
 #include "content/common/notification_details.h"
@@ -142,7 +143,7 @@ class MockCloudPrintDataSenderHelper : public CloudPrintDataSenderHelper {
                                             const Value& arg2));
 };
 
-class CloudPrintURLTest : public testing::Test {
+class CloudPrintURLTest : public TestingBrowserProcessTest {
  public:
   CloudPrintURLTest() {}