Create c/b/ui/cocoa/test and move test files to there

chrome/browser/ui/cocoa/run_loop_testing.h

Index: chrome/browser/ui/cocoa/run_loop_testing.h
diff --git a/chrome/browser/ui/cocoa/run_loop_testing.h b/chrome/browser/ui/cocoa/run_loop_testing.h
deleted file mode 100644
index 5269787162b570154776b4d8edda146547caa0dc..0000000000000000000000000000000000000000
--- a/chrome/browser/ui/cocoa/run_loop_testing.h
+++ /dev/null
@@ -1,29 +0,0 @@
-// Copyright (c) 2011 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_BROWSER_UI_COCOA_RUN_LOOP_TESTING_H_
-#define CHROME_BROWSER_UI_COCOA_RUN_LOOP_TESTING_H_
-
-namespace chrome {
-namespace testing {
-
-// A common pattern in Chromium is to get a selector to execute on the next
-// iteration of the outermost run loop, done like so:
-//
-//    [someObj performSelector:@selector(someSel:) withObject:nil afterDelay:0];
-//
-// This is used when performing the work will negatively affect something
-// currently on the stack. Unfortunately this also affects the testability of
-// objects that do this. A call to this function will pump work like this from
-// the event queue and run it until all such work, as of the time of calling
-// this, has been processed.
-//
-// Note that this is not a NSApplication-based loop, and so things like NSEvents
-// are *not* pumped from the event queue.
-void NSRunLoopRunAllPending();
-
-}  // namespace testing
-}  // namespace chrome
-
-#endif  // CHROME_BROWSER_UI_COCOA_RUN_LOOP_TESTING_H_