Initialize the message center as part of the testing browser process

chrome/browser/notifications/message_center_notifications_unittest.cc

Index: chrome/browser/notifications/message_center_notifications_unittest.cc
diff --git a/chrome/browser/notifications/message_center_notifications_unittest.cc b/chrome/browser/notifications/message_center_notifications_unittest.cc
index 742031378daffea905c851c2aa577578d4c2f5a4..a041b0b1ffa2036e832651453034e66aed2305aa 100644
--- a/chrome/browser/notifications/message_center_notifications_unittest.cc
+++ b/chrome/browser/notifications/message_center_notifications_unittest.cc
@@ -44,13 +44,6 @@ class MessageCenterNotificationManagerTest : public BrowserWithTestWindowTest {
  protected:
   void SetUp() override {
     BrowserWithTestWindowTest::SetUp();
-#if !defined(OS_CHROMEOS)
-    // BrowserWithTestWindowTest owns an AshTestHelper on OS_CHROMEOS, which
-    // in turn initializes the message center.  On other platforms, we need to
-    // initialize it here.
-    MessageCenter::Initialize();
-#endif
-
 
     TestingBrowserProcess* browser_process = TestingBrowserProcess::GetGlobal();
     profile_manager_.reset(new TestingProfileManager(browser_process));
@@ -64,11 +57,6 @@ class MessageCenterNotificationManagerTest : public BrowserWithTestWindowTest {
   void TearDown() override {
     profile_manager_.reset();
 
-#if !defined(OS_CHROMEOS)
-    // Shutdown the message center if we initialized it manually.
-    MessageCenter::Shutdown();
-#endif
-
     BrowserWithTestWindowTest::TearDown();
   }