Google Git
Sign in
pigweed / third_party / github / google / googletest / 5fce13091d223069436ad7a5aad53f026b0f2041
commit5fce13091d223069436ad7a5aad53f026b0f2041[log] [tgz]
authorAaron Jacobs <jacobsa@google.com>Wed Mar 22 20:19:06 2023 -0700
committerCopybara-Service <copybara-worker@google.com>Wed Mar 22 20:19:44 2023 -0700
tree616ce824189315035025f25977ebcc0a5be59859
parent974e18ee6f146a2418f9cea83170c640e7d622d6 [diff]
gtest.cc: add a newline after a failure when there is no OS stack trace.

This makes the behavior consistent when GTEST_STACK_TRACE_DEPTH is set to zero
and not: there is always vertical whitespace separating failure messages.

PiperOrigin-RevId: 518744611
Change-Id: I5b4af40633849850660504c3f497a76601d4311d
5 files changed
tree: 616ce824189315035025f25977ebcc0a5be59859
  1. .github/
  2. ci/
  3. docs/
  4. googlemock/
  5. googletest/
  6. .clang-format
  7. .gitignore
  8. BUILD.bazel
  9. CMakeLists.txt
  10. CONTRIBUTING.md
  11. CONTRIBUTORS
  12. googletest_deps.bzl
  13. LICENSE
  14. README.md
  15. WORKSPACE
README.md

GoogleTest

Announcements

Live at Head

GoogleTest now follows the Abseil Live at Head philosophy. We recommend updating to the latest commit in the main branch as often as possible.

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.13.0

Release 1.13.0 is now available.

The 1.13.x branch requires at least C++14.

Continuous Integration

We use Google's internal systems for continuous integration.
GitHub Actions were added for the convenience of open source contributors. They are exclusively maintained by the open source community and not used by the GoogleTest team.

Coming Soon

  • We are planning to take a dependency on Abseil.
  • More documentation improvements are planned.

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

  • An xUnit test framework.
  • Test discovery.
  • A rich set of assertions.
  • User-defined assertions.
  • Death tests.
  • Fatal and non-fatal failures.
  • Value-parameterized tests.
  • Type-parameterized tests.
  • Various options for running the tests.
  • XML test report generation.

Supported Platforms

GoogleTest follows Google's Foundational C++ Support Policy. See this table for a list of currently supported versions 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:

Related Open Source 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!