Google Test
GoogleTest - Google Testing and Mocking Framework (by google)
CppUTest
CppUTest unit testing and mocking framework for C/C++ (by cpputest)
Google Test | CppUTest | |
---|---|---|
73 | 2 | |
36,950 | 1,442 | |
1.2% | 0.3% | |
7.5 | 7.8 | |
8 days ago | about 1 month ago | |
C++ | C++ | |
BSD 3-clause "New" or "Revised" License | BSD 3-clause "New" or "Revised" License |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Google Test
Posts with mentions or reviews of Google Test.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2025-05-10.
-
CLion agora é gratuito!
A versão inicial oferece suporte aos compiladores GNU Compiler Collection (GCC) e Clang e ao depurador GDB, LLDB e Google Test.
-
Why I Built a New C++ Build System
[dependency] https://github.com/google/googletest
-
The Two Factions of C++
> Googletest ... declares a direct dependency on an older LTS release of absl
Looking at the build configuration code:
https://github.com/google/googletest/blob/main/CMakeLists.tx...
it seems like the dependence on Abseil is optional. i.e. you can use googltest on its own. I wouldn't recommend it (I kinda like doctest), but still.
-
Getting started with GoogleTest and CMake
include(FetchContent) # Fetch GoogleTest FetchContent_Declare( googletest GIT_REPOSITORY https://github.com/google/googletest.git GIT_TAG release-1.11.0 ) FetchContent_MakeAvailable(googletest) # Collect C++ source files recursively file(GLOB_RECURSE CXX_FILES "${CMAKE_CURRENT_LIST_DIR}/*.cpp") add_executable(unit_tests ${CXX_FILES}) # Link GoogleTest libraries target_link_libraries(unit_tests PRIVATE gtest_main ${PROJECT_NAME}_lib # Link to the main project library ) # Include directories (including where GoogleTest is built) target_include_directories(unit_tests PRIVATE ${gtest_SOURCE_DIR}/include) # Add include directories for tests to find headers target_include_directories(unit_tests PRIVATE ${PROJECT_SOURCE_DIR}/src) # Enable testing and discover tests # Discover and run tests include(GoogleTest) gtest_discover_tests(unit_tests)
-
Open Source C++ Stack
Google Test
-
Creating k-NN with C++ (from Scratch)
cmake_minimum_required(VERSION 3.5) project(knn_cpp CXX) include(FetchContent) FetchContent_Declare( googletest GIT_REPOSITORY https://github.com/google/googletest.git GIT_TAG release-1.11.0 ) FetchContent_MakeAvailable(googletest) FetchContent_Declare(matplotplusplus GIT_REPOSITORY https://github.com/alandefreitas/matplotplusplus GIT_TAG origin/master) FetchContent_GetProperties(matplotplusplus) if(NOT matplotplusplus_POPULATED) FetchContent_Populate(matplotplusplus) add_subdirectory(${matplotplusplus_SOURCE_DIR} ${matplotplusplus_BINARY_DIR} EXCLUDE_FROM_ALL) endif() function(knn_cpp_test TEST_NAME TEST_SOURCE) add_executable(${TEST_NAME} ${TEST_SOURCE}) target_link_libraries(${TEST_NAME} PUBLIC matplot) aux_source_directory(${CMAKE_CURRENT_SOURCE_DIR}/../lib LIB_SOURCES) target_link_libraries(${TEST_NAME} PRIVATE gtest gtest_main gmock gmock_main) target_include_directories(${TEST_NAME} PRIVATE ${CMAKE_CURRENT_SOURCE_DIR} ${CMAKE_CURRENT_SOURCE_DIR}/../) target_sources(${TEST_NAME} PRIVATE ${LIB_SOURCES} ) include(GoogleTest) gtest_discover_tests(${TEST_NAME}) endfunction() knn_cpp_test(LinearAlgebraTest la_test.cc) knn_cpp_test(KnnTest knn_test.cc) knn_cpp_test(UtilsTest utils_test.cc)
-
Starting with C
Okay, time to start unit tests!!! We will use Unity Test Framework to do unit testing. It is one of widely used testing frameworks alongside with Check, Google Test etc. Just downloading source code, and putting it to the project folder is enough to make it work (that is also why it is portable).
-
Just in case: Debian Bookworm comes with a buggy GCC
Updating GCC (it happened to GoogleTest).
-
Automatically run tests, formatters & linters with CI!
Roy's project uses Google Test, a C++ testing framework. His testing setup is similar to mine as we both keep source files in one directory and tests in another. The key difference is that I can run the tests using the Visual Studios run button. It was fairly easy to write the new tests as there were existing ones that I could reference to check the syntax!
-
C++ Unit Testing Using Google Test - My Experience
The Google Test Documentation provides a primer for first-time users. The primer introduces some basic concepts and terminology, some of which I've been able to learn for this lab exercise.
CppUTest
Posts with mentions or reviews of CppUTest.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2025-06-16.
-
CI Server for embedded systems based on Raspberry Pi
sudo apt install -y autoconf libtool && sudo git clone https://github.com/cpputest/cpputest.git /opt/cpputest && sudo chown -R $(whoami):$(whoami) /opt/cpputest && cd /opt/cpputest && autoreconf . -i && ./configure && make tdd && echo 'export CPPUTEST_HOME=/opt/cpputest' >> ~/.bashrc && source ~/.bashrc
-
Tool Containerization Best Practices For Embedded Software Development
# Use the Debian base image as our starting point. FROM debian:bullseye # Install the required packages. RUN apt update -y && \ apt -y install g++=4:10.2.1-1 \ cmake=3.18.4-2+deb11u1 \ libtool=2.4.6-15 \ autoconf=2.69-14 \ git=1:2.30.2-1+deb11u2 \ gdb=10.1-1.7 \ wget=1.21-1+deb11u1 \ bzip2=1.0.8-4 \ make=4.3-4.1 \ stlink-tools=1.6.1+ds-3 # Clone and install CppUTest RUN git clone https://github.com/cpputest/cpputest WORKDIR /cpputest RUN autoreconf . -i && \ ./configure && \ make tdd ENV CPPUTEST_HOME=/cpputest # Set the working directory for your project WORKDIR /work # Download and set up the GNU Arm toolchain RUN wget https://developer.arm.com/-/media/Files/downloads/gnu-rm/10.3-2021.10/gcc-arm-none-eabi-10.3-2021.10-x86_64-linux.tar.bz2 && \ tar -xjf gcc-arm-none-eabi-10.3-2021.10-x86_64-linux.tar.bz2 && \ rm gcc-arm-none-eabi-10.3-2021.10-x86_64-linux.tar.bz2 && \ mv gcc-arm-none-eabi-10.3-2021.10 /opt/gcc-arm ENV PATH="/opt/gcc-arm/bin:${PATH}"
What are some alternatives?
When comparing Google Test and CppUTest you can also consider the following projects:
Catch - A modern, C++-native, test framework for unit-tests, TDD and BDD - using C++14, C++17 and later (C++11 support is in v2.x branch, and C++03 on the Catch1.x branch)
CppUnit - C++ port of JUnit
Unity Test API - Simple unit testing for C
doctest - The fastest feature-rich C++11/14/17/20/23 single-header testing framework
fff - A testing micro framework for creating function test doubles