File: run_loop_testing.h

package info (click to toggle)
chromium 139.0.7258.127-1
  • links: PTS, VCS
  • area: main
  • in suites:
  • size: 6,122,068 kB
  • sloc: cpp: 35,100,771; ansic: 7,163,530; javascript: 4,103,002; python: 1,436,920; asm: 946,517; xml: 746,709; pascal: 187,653; perl: 88,691; sh: 88,436; objc: 79,953; sql: 51,488; cs: 44,583; fortran: 24,137; makefile: 22,147; tcl: 15,277; php: 13,980; yacc: 8,984; ruby: 7,485; awk: 3,720; lisp: 3,096; lex: 1,327; ada: 727; jsp: 228; sed: 36
file content (29 lines) | stat: -rw-r--r-- 1,119 bytes parent folder | download | duplicates (7) 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
 
// Copyright 2011 The Chromium Authors
// 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_TEST_RUN_LOOP_TESTING_H_
#define CHROME_BROWSER_UI_COCOA_TEST_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_TEST_RUN_LOOP_TESTING_H_