GoogleTest - Google Testing and Mocking Framework
Go to file
Nithin 24ee021f44
Don't repeat the failure summary in the XML report body
The XML printer puts the summary of a test part result into the "message"
attribute of the <failure> or <skipped> element and the full message into
the CDATA body of that same element. The two only differ when the message
carries a stack trace, so in a build without stack trace support, and for
every skipped result since those never get a trace, the report contains
the exact same text twice.

Write the CDATA body only when it holds more than the attribute already
does. The "message" attribute keeps the summary, which is what JUnit
consumers read, and nothing is dropped from the report. The JSON printer
already reports the message just once.

Fixes #4785
2026-08-19 23:02:54 +05:30
.github/ISSUE_TEMPLATE Delete the unofficial GitHub actions tests. 2024-04-03 07:06:06 -07:00
ci Remove -WX to prevent compilation errors for users when a symbol becomes deprecated 2026-08-06 13:13:43 -07:00
docs Don't repeat the failure summary in the XML report body 2026-08-19 23:02:54 +05:30
googlemock Remove wchar_t overloads if `GTEST_HAS_STD_WSTRING` is disabled 2026-08-17 10:35:06 -07:00
googletest Don't repeat the failure summary in the XML report body 2026-08-19 23:02:54 +05:30
.clang-format Googletest export 2021-01-15 15:53:39 -05:00
.gitignore Add support for Bzlmod for the next release 2024-01-25 10:27:52 -08:00
BUILD.bazel Add alwayslink = True to //:gtest_main 2025-11-04 19:42:58 +01:00
CMakeLists.txt chore: bump main branch version to 1.18.0 2026-07-05 08:54:29 +05:30
CONTRIBUTING.md Merge pull request #4343 from sthd:http-to-https 2023-08-22 10:24:02 -07:00
CONTRIBUTORS Add myself to Contributors 2024-01-31 21:11:21 +09:00
LICENSE Wrong LICENSE file, sorry. Corrected. [skip ci] 2017-12-08 23:16:46 -05:00
MODULE.bazel Update GoogleTest dependencies in preparation for release 2026-08-05 12:29:28 -07:00
README.md Update version strings to 1.18 2026-08-11 06:59:21 -07:00
WORKSPACE Update GoogleTest dependencies in preparation for release 2026-08-05 12:29:28 -07:00
WORKSPACE.bzlmod Add support for Bzlmod for the next release 2024-01-25 10:27:52 -08:00
fake_fuchsia_sdk.bzl Put the fake Fuchsia SDK in a module extension 2024-12-23 13:33:10 -08:00
googletest_deps.bzl Upgrade most builds to use Bazel 9.0.0 2026-02-05 08:42:50 -08:00

README.md

GoogleTest

Announcements

Documentation Updates

Our documentation is now live on GitHub Pages at https://google.github.io/googletest/. We recommend browsing the documentation on GitHub Pages rather than directly in the repository.

Release 1.18.0

Release 1.18.0 is now available.

The 1.18.x branch requires at least C++17.

Continuous Integration

We use Google's internal systems for continuous integration.

Coming Soon

  • We are planning to take a dependency on Abseil.

Welcome to GoogleTest, Google's C++ test framework!

This repository is a merger of the formerly separate GoogleTest and GoogleMock projects. These were so closely related that it makes sense to maintain and release them together.

Getting Started

See the GoogleTest User's Guide for documentation. We recommend starting with the GoogleTest Primer.

More information about building GoogleTest can be found at googletest/README.md.

Features

  • xUnit test framework:
    Googletest is based on the xUnit testing framework, a popular architecture for unit testing.
  • Test discovery:
    Googletest automatically discovers and runs your tests, eliminating the need to manually register your tests.
  • Rich set of assertions:
    Googletest provides a variety of assertions, such as equality, inequality, exceptions, and more, making it easy to test your code.
  • User-defined assertions:
    You can define your own assertions with Googletest, making it simple to write tests that are specific to your code.
  • Death tests:
    Googletest supports death tests, which verify that your code exits in a certain way, making it useful for testing error-handling code.
  • Fatal and non-fatal failures:
    You can specify whether a test failure should be treated as fatal or non-fatal with Googletest, allowing tests to continue running even if a failure occurs.
  • Value-parameterized tests:
    Googletest supports value-parameterized tests, which run multiple times with different input values, making it useful for testing functions that take different inputs.
  • Type-parameterized tests:
    Googletest also supports type-parameterized tests, which run with different data types, making it useful for testing functions that work with different data types.
  • Various options for running tests:
    Googletest provides many options for running tests including running individual tests, running tests in a specific order and running tests in parallel.

Supported Platforms

GoogleTest follows Google's Foundational C++ Support Policy. See this table for a list of currently supported versions of compilers, platforms, and build tools.

Who Is Using GoogleTest?

In addition to many internal projects at Google, GoogleTest is also used by the following notable projects:

GTest Runner is a Qt5 based automated test-runner and Graphical User Interface with powerful features for Windows and Linux platforms.

GoogleTest UI is a test runner that runs your test binary, allows you to track its progress via a progress bar, and displays a list of test failures. Clicking on one shows failure text. GoogleTest UI is written in C#.

GTest TAP Listener is an event listener for GoogleTest that implements the TAP protocol for test result output. If your test runner understands TAP, you may find it useful.

gtest-parallel is a test runner that runs tests from your binary in parallel to provide significant speed-up.

GoogleTest Adapter is a VS Code extension allowing to view GoogleTest in a tree view and run/debug your tests.

C++ TestMate is a VS Code extension allowing to view GoogleTest in a tree view and run/debug your tests.

Cornichon is a small Gherkin DSL parser that generates stub code for GoogleTest.

Contributing Changes

Please read CONTRIBUTING.md for details on how to contribute to this project.

Happy testing!