// Copyright 2014 The Crashpad Authors // // Licensed under the Apache License, Version 2.0 (the "License"); // you may not use this file except in compliance with the License. // You may obtain a copy of the License at // // http://www.apache.org/licenses/LICENSE-2.0 // // Unless required by applicable law or agreed to in writing, software // distributed under the License is distributed on an "AS IS" BASIS, // WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. // See the License for the specific language governing permissions and // limitations under the License. #ifndef CRASHPAD_TEST_MULTIPROCESS_EXEC_H_ #define CRASHPAD_TEST_MULTIPROCESS_EXEC_H_ #include <string> #include <vector> #include "base/files/file_path.h" #include "build/build_config.h" #include "test/multiprocess.h" #include "test/process_type.h" //! \file namespace crashpad { namespace test { namespace internal { //! \brief Command line argument used to indicate that a child test function //! should be run. constexpr char kChildTestFunction[] = …; //! \brief Helper class used by CRASHPAD_CHILD_TEST_MAIN() to insert a child //! function into the global mapping. class AppendMultiprocessTest { … }; //! \brief Used to run a child test function by name, registered by //! CRASHPAD_CHILD_TEST_MAIN(). //! //! \return The exit code of the child process after running the function named //! by \a test_name. Aborts with a CHECK() if \a test_name wasn't //! registered. int CheckedInvokeMultiprocessChild(const std::string& test_name); } // namespace internal //! \brief Registers a function that can be invoked as a child process by //! MultiprocessExec. //! //! Used as: //! //! \code //! CRASHPAD_CHILD_TEST_MAIN(MyChildTestBody) { //! ... child body ... //! } //! \endcode //! //! In the main (parent) test body, this function can be run in a child process //! via MultiprocessExec::SetChildTestMainFunction(). #define CRASHPAD_CHILD_TEST_MAIN(test_main) … //! \brief Manages an `exec()`-based multiprocess test. //! //! These tests are based on `fork()` and `exec()`. The parent process is able //! to communicate with the child in the same manner as a base-class //! Multiprocess parent. The read and write pipes appear in the child process on //! stdin and stdout, respectively. //! //! Subclasses are expected to implement the parent in the same was as a //! base-class Multiprocess parent. The child must be implemented in an //! executable to be set by SetChildCommand(). class MultiprocessExec : public Multiprocess { … }; } // namespace test } // namespace crashpad #endif // CRASHPAD_TEST_MULTIPROCESS_EXEC_H_