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

chrome/test/base/in_process_browser_test.h

Index: chrome/test/base/in_process_browser_test.h
diff --git a/chrome/test/base/in_process_browser_test.h b/chrome/test/base/in_process_browser_test.h
index c6eb60acfef10fc61f1b9ea4133897939ff6171c..e516f4ead1ae3bbd538eb9276b2ec54bb09d6b6f 100644
--- a/chrome/test/base/in_process_browser_test.h
+++ b/chrome/test/base/in_process_browser_test.h
@@ -34,6 +34,9 @@ class ScopedCOMInitializer;
 
 class Browser;
 class Profile;
+#if defined(OS_MACOSX)
+class ScopedBundleSwizzlerMac;
+#endif  // defined(OS_MACOSX)
 
 namespace content {
 class ContentRendererClient;
@@ -224,6 +227,7 @@ class InProcessBrowserTest : public content::BrowserTestBase {
 
 #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)