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

content/common/notification_service_unittest.cc

Index: content/common/notification_service_unittest.cc
diff --git a/content/common/notification_service_unittest.cc b/content/common/notification_service_unittest.cc
index a40e11c0e9487d4697fff11ede08836588a9762f..b673007a0ab8b16b4f1dd93077962c4bba54c8cb 100644
--- a/content/common/notification_service_unittest.cc
+++ b/content/common/notification_service_unittest.cc
@@ -5,6 +5,7 @@
 #include "content/common/notification_observer.h"
 #include "content/common/notification_registrar.h"
 #include "content/common/notification_service.h"
+#include "chrome/test/testing_browser_process_test.h"

[sky, 2011/07/28 00:28:03]

nit: before content

 #include "testing/gtest/include/gtest/gtest.h"
 
 namespace {
@@ -31,7 +32,7 @@ private:
 }  // namespace
 
 
-class NotificationServiceTest : public testing::Test {
+class NotificationServiceTest : public TestingBrowserProcessTest {

[jam, 2011/07/28 01:41:21]

why should a unit test derive from BrowserProcessTest? or is that something
you'll do in a future cl?

[Paweł Hajdan Jr., 2011/07/28 03:49:18]

TestingBrowserProcess has nothing to do with browser tests or
InProcessBrowserTest. Sorry for the confusion; the main idea here is that we
mock out the BrowserProcess object stored in g_browser_process.

[jam, 2011/07/28 16:48:54]

I see, although I'm not sure I understand why unit tests need a BrowserProcess
object around. But we can leave this until we start working on content_unittests

  protected:
   NotificationRegistrar registrar_;
 };