File: multiprocess_func_list.h

package info (click to toggle)
chromium 145.0.7632.159-1
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid
  • size: 5,976,224 kB
  • sloc: cpp: 36,198,469; ansic: 7,634,080; javascript: 3,564,060; python: 1,649,622; xml: 838,470; asm: 717,087; pascal: 185,708; sh: 88,786; perl: 88,718; objc: 79,984; sql: 59,811; cs: 42,452; fortran: 24,101; makefile: 21,144; tcl: 15,277; php: 14,022; yacc: 9,066; ruby: 7,553; awk: 3,720; lisp: 3,233; lex: 1,328; ada: 727; jsp: 228; sed: 36
file content (78 lines) | stat: -rw-r--r-- 2,978 bytes parent folder | download | duplicates (10)
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
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
// Copyright 2012 The Chromium Authors
// Use of this source code is governed by a BSD-style license that can be
// found in the LICENSE file.

#ifndef TESTING_MULTIPROCESS_FUNC_LIST_H_
#define TESTING_MULTIPROCESS_FUNC_LIST_H_

#include <string>

// This file provides the plumbing to register functions to be executed
// as the main function of a child process in a multi-process test.
// This complements the MultiProcessTest class which provides facilities
// for launching such tests.
//
// The MULTIPROCESS_TEST_MAIN() macro registers a string -> func_ptr mapping
// by creating a new global instance of the AppendMultiProcessTest() class
// this means that by the time that we reach our main() function the mapping
// is already in place.
//
// Example usage:
//  MULTIPROCESS_TEST_MAIN(a_test_func) {
//    // Code here runs in a child process.
//    return 0;
//  }
//
// The prototype of a_test_func is implicitly
//   int test_main_func_name();

namespace multi_process_function_list {

// Type for child process main functions.
typedef int (*TestMainFunctionPtr)();

// Type for child setup functions.
typedef void (*SetupFunctionPtr)();

// Helper class to append a test function to the global mapping.
// Used by the MULTIPROCESS_TEST_MAIN macro.
class AppendMultiProcessTest {
 public:
  // |main_func_ptr| is the main function that is run in the child process.
  // |setup_func_ptr| is a function run when the global mapping is added.
  AppendMultiProcessTest(std::string test_name,
                         TestMainFunctionPtr main_func_ptr,
                         SetupFunctionPtr setup_func_ptr);
};

using ChildProcessTestRunner = int (*)(const std::string&);
void SetChildProcessTestRunner(ChildProcessTestRunner runner);

// Invokes the ChildProcessTestRunner callback with `test_name` if the callback
// is not null. Otherwise invokes test associated main function previously
// registered with MULTIPROCESS_TEST_MAIN().
int InvokeChildProcessTest(const std::string& test_name);

// Invokes a the main function of a test previously registered with
// MULTIPROCESS_TEST_MAIN().
int InvokeChildProcessTestMain(const std::string& test_name);

// This macro creates a global MultiProcessTest::AppendMultiProcessTest object
// whose constructor does the work of adding the global mapping.
#define MULTIPROCESS_TEST_MAIN(test_main) \
  MULTIPROCESS_TEST_MAIN_WITH_SETUP(test_main, NULL)

// Same as above but lets callers specify a setup method that is run in the
// child process, just before the main function is run.  This facilitates
// adding a generic one-time setup function for multiple tests.
#define MULTIPROCESS_TEST_MAIN_WITH_SETUP(test_main, test_setup) \
  int test_main(); \
  namespace { \
    multi_process_function_list::AppendMultiProcessTest \
    AddMultiProcessTest##_##test_main(#test_main, (test_main), (test_setup)); \
  } \
  int test_main()

}  // namespace multi_process_function_list

#endif  // TESTING_MULTIPROCESS_FUNC_LIST_H_