Ensures NOTIFICATION_APP_TERMINATING at the end of InProcessBrowserTest.

chrome/test/base/in_process_browser_test.cc

Index: chrome/test/base/in_process_browser_test.cc
diff --git a/chrome/test/base/in_process_browser_test.cc b/chrome/test/base/in_process_browser_test.cc
index 014386cc509d1cf70126790a46ea1ce6aa7d0e4a..47e8c2a6fee41c9d9cab70b6d4caea436e7c26ab 100644
--- a/chrome/test/base/in_process_browser_test.cc
+++ b/chrome/test/base/in_process_browser_test.cc
@@ -458,8 +458,10 @@ void InProcessBrowserTest::RunTestOnMainThreadLoop() {
 }
 
 void InProcessBrowserTest::QuitBrowsers() {
-  if (chrome::GetTotalBrowserCount() == 0)
+  if (chrome::GetTotalBrowserCount() == 0) {
+    chrome::NotifyAppTerminating();

[sky, 2013/09/05 15:33:45]

Might this result in sending out notification twice?

[Jun Mukai, 2013/09/05 18:46:56]

No, as far as I see.

Usually app-terminating will be emitted through chrome::AttemptExit() below, and
I cannot find no other code paths to emit it. I also injected a log into
NotifyAppTerminating(), and at least some test doesn't print the log.

It also seems that NotifyAppTerminating() uses a static boolean flag to avoid
notifying twice, so I think it's safe.

     return;
+  }
 
   // Invoke AttemptExit on a running message loop.
   // AttemptExit exits the message loop after everything has been