mac: Swizzle out +[NSBundle mainBundle] for in process browser tests.

chrome/test/base/in_process_browser_test.h

 // Copyright (c) 2012 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 #ifndef CHROME_TEST_BASE_IN_PROCESS_BROWSER_TEST_H_
 #define CHROME_TEST_BASE_IN_PROCESS_BROWSER_TEST_H_
 
 #include "base/compiler_specific.h"
 #include "base/files/scoped_temp_dir.h"
 #include "base/memory/ref_counted.h"
@@ skipping 16 matching lines @@
 
 #if defined(OS_WIN)
 namespace win {
 class ScopedCOMInitializer;
 }
 #endif  // defined(OS_WIN)
 }  // namespace base
 
 class Browser;
 class Profile;
+#if defined(OS_MACOSX)
+class ScopedBundleSwizzlerMac;
+#endif  // defined(OS_MACOSX)
 
 namespace content {
 class ContentRendererClient;
 }
 
 // Base class for tests wanting to bring up a browser in the unit test process.
 // Writing tests with InProcessBrowserTest is slightly different than that of
 // other tests. This is necessitated by InProcessBrowserTest running a message
 // loop. To use InProcessBrowserTest do the following:
 // . Use the macro IN_PROC_BROWSER_TEST_F to define your test.
@@ skipping 170 matching lines @@
   // True if this is a multi-desktop test (in which case this browser test will
   // not ensure that Browsers are only created on the tested desktop).
   bool multi_desktop_test_;
 
   // True if the accessibility test should run for a particular test case.
   // This is reset for every test case.
   bool run_accessibility_checks_for_test_case_;
 
 #if defined(OS_MACOSX)
   base::mac::ScopedNSAutoreleasePool* autorelease_pool_;
+  scoped_ptr<ScopedBundleSwizzlerMac> bundle_swizzler_;

[Paweł Hajdan Jr., 2015/07/08 10:01:13]

Wouldn't the same apply to say content_browsertests?

I wonder why not make the change in content::BrowserTestBase instead.

[erikchen, 2015/07/08 17:48:38]

I don't believe so.

If you look at content_browsertests on the FYI waterfall, there's only 1
test-suite that fails, and it appears to be related to AppKit. 
http://build.chromium.org/p/chromium.fyi/builders/Chromium%20Mac%2010.10/buil...

I'm guessing that content_browsertests has sufficiently few dependencies on
AppKit that the swizzler is not necessary.

 #endif  // OS_MACOSX
 
 #if defined(OS_WIN)
   scoped_ptr<base::win::ScopedCOMInitializer> com_initializer_;
 #endif
 };
 
 #endif  // CHROME_TEST_BASE_IN_PROCESS_BROWSER_TEST_H_