CppUMockGen | Mock generator for CppUTest/CppUMock | Mock library

The last releases for Windows and Linux can be found in [GitHub Releases](https://github.com/jgonzalezdr/CppUMockGen/releases) in different formats: - Installer for Windows (x64). - Portable package for Windows (x64). - Debian package for Linux (x64), tested on Ubuntu 18.04 LTS. - Portable package for Linux (x64). On Ubuntu systems you can install CppUMockGen from the [CppUMockGen PPA repository](https://launchpad.net/~jgonzalezdr/+archive/ubuntu/cpputest).
| OPTION | Description | | - | - | | -i, --input <input> ` | Input file path | | `-m, --mock-output <mock-output> | Mock output directory or file path | | -e, --expect-output <expect-output> | Expectation output directory or file path | | -x, --cpp | Force interpretation of the input file as C++ | | -s, --std | Set language standard (c+\+14, c\+\+17, etc.)| | -I, --include-path <path> | Include path | | -B, --base-directory <path> | Base directory path | | -t, --type-override <expr> | Override generic type | | -f, --config-file <file> | Configuration file to be parsed for options | | -v, --version | Print version | | -h, --help | Print help |. To generate a mock from a header file containing the functions that you want to mock, just pass the path to the header file as input in the first non-option argument or explicitly with the -i / --input option, and the path where you want the file with the mocked functions to be generated as output using the -m / --mock-output option. To generate expectations, pass the path where you want the files with the expectation to be generated as output using the -e / --expect-output option (additionally to or instead of the -m option). CppUMockGen, just as any C/C++ compiler, needs to know where to find other include files referenced by the input file in order to interpret it properly. Pass the paths to the necessary include directories by using the -I / --include-path option. Like with most compilers, you may use this option several times to indicate multiple include directories. Mocks and expectations generated by CppUMockGen need to include the mocked header file. By default, the mocked header file will be referenced with a relative path from the directory where the mocks/expectations are generated. This behavior may be overriden using the -B / --base-directory option to set a base directory to reference included mocked headers (e.g., set it to a directory that is in the include path when compiling tests). CppUMockGen deduces the data types to use with CppUMock from the actual function parameters and return types. If the API that you are mocking is well designed (e.g. pointers to non-const values are not used for input parameters), CppUMockGen will guess properly in most cases the correct types. Nevertheless, mocked data types can be overridden by using -t / --type-override options to indicate the type of function parameters or function returns. Type overriding can be defined in generic form, which apply to any function parameter or return types that match the specified type, or can be defined in function-specific form, which apply to parameters and return types of the specified function. Since complex mocks will require a lot of override options, and many of them can be reused to generate mocks for other files, you can store options in a text file and load that file using the -f / --config-file option.
To build CppUMockGen first clone this repository on your machine, and in the directory where you cloned it (top directory) execute the following commands:.
To build CppUMockGen first clone this repository on your machine, and in the directory where you cloned it (top directory) execute the following commands (where <Visual Studio XX 20YY> is a cmake generator for visual studio, e.g., "Visual Studio 16 2019", "Visual Studio 17 2022"):. Eventually open the CppUMockGen.Top.sln VS solution generated in the build_vs directory, then compile the solution. To execute the tests, compile the run_tests project. If coverage is enabled, to generate the coverage report compile the run_coverage project, and the report will be generated in the coverage_msvc directory under the top directory.
To build CppUMockGen first clone this repository on your machine, and in the directory where you cloned it (top directory) execute the following commands:.
The following build types are supported: - Release - Debug - RelWithDebInfo (Release build with debug information) - MinSizeRel (Release with executable size minimization) - Coverage (Only GCC/MinGW). When using Visual Studio, the available build types are available as project configurations. Coverage is enabled by default, to disable it pass the option -DCOVERAGE=OFF to CMake. When using GCC/MinGW, the default build type is Release. To select a different build type pass the option -DCMAKE_BUILD_TYPE=<Build Type> to CMake. If during configuration CMake cannot find some dependencies, their installation paths can be indicated by passing one of the following options to CMake: - libClang: -DLibClang_HOME=<Path to LLVM top directory> - CppUTest: -DCppUTest_HOME=<Path to CppUTest top directory> - LCOV: -Dlcov_HOME=<Path to LCOV top directory>.