ImportantFileWriter: check return value of PostTask...

chrome/browser/extensions/extension_menu_manager_unittest.cc

Index: chrome/browser/extensions/extension_menu_manager_unittest.cc
===================================================================
--- chrome/browser/extensions/extension_menu_manager_unittest.cc	(revision 77440)
+++ chrome/browser/extensions/extension_menu_manager_unittest.cc	(working copy)
@@ -31,8 +31,11 @@
 // Base class for tests.
 class ExtensionMenuManagerTest : public testing::Test {
  public:
-  ExtensionMenuManagerTest() : next_id_(1) {}
-  ~ExtensionMenuManagerTest() {}
+  ExtensionMenuManagerTest()
+      : ui_thread_(BrowserThread::UI, &message_loop_),
+        file_thread_(BrowserThread::FILE, &message_loop_),

[asargent_no_longer_on_chrome, 2011/03/09 20:53:17]

same message loop to 2 threads?

[Paweł Hajdan Jr., 2011/03/10 07:30:35]

In this case I'm absolutely sure this is valid. Here's how it works:

There are no two threads here, only one. There are two "labels" though, UI and
FILE. In the browser those are all real threads of course, each with its own
message loop. For tests however, it is often simpler to have just one message
loop (it also makes the test more deterministic).

BrowserThread maps thread labels (UI, FILE, IO and so on) to MessageLoops. It
can be seen as sort of a switchboard. Now when I'm using same message loop for 2
thread labels I'm saying I just don't want to create more threads, and I want
everything to run on the same thread.

Short story: it would be incorrect in the browser code, but in test code it is
perfectly fine, and makes things simpler. There are many other existing tests
doing so already.

+        next_id_(1) {
+  }
 
   // Returns a test item.
   ExtensionMenuItem* CreateTestItem(Extension* extension) {
@@ -51,6 +54,10 @@
   }
 
  protected:
+  MessageLoopForUI message_loop_;
+  BrowserThread ui_thread_;
+  BrowserThread file_thread_;
+
   ExtensionMenuManager manager_;
   ExtensionList extensions_;
   TestExtensionPrefs prefs_;
@@ -409,9 +416,6 @@
 }
 
 TEST_F(ExtensionMenuManagerTest, ExecuteCommand) {
-  MessageLoopForUI message_loop;
-  BrowserThread ui_thread(BrowserThread::UI, &message_loop);
-
   MockTestingProfile profile;
 
   scoped_ptr<MockExtensionEventRouter> mock_event_router(