| commit | 25dcdc7e8bfac8967f20fb2c0a628f5cf442188d | [log] [tgz] |
|---|---|---|
| author | Derek Mauro <dmauro@google.com> | Mon Apr 04 07:38:23 2022 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Mon Apr 04 07:39:03 2022 -0700 |
| tree | 0bd2bf078f5491dfd089dc0fab194b805788d622 | |
| parent | af29db7ec28d6df1c7f0f745186884091e602e07 [diff] |
Use the Abseil flags library when Abseil is present
When built with `--define=absl=1` under Bazel, GoogleTest
flags use ABSL_FLAG instead of GoogleTest's own implementation.
There are some minor behavior differences in this mode.
The most notable difference is that unrecognized flags result
in a flag parsing error, and are not returned to the user though
a modified argc/argv, unless they appear after the positional
argument delimiter ("--").
For example, to pass a non-Abseil flag, you would have to do
./mytest --gtest_color=false -- --myflag=myvalue
The documentation at https://abseil.io/docs/cpp/guides/flags
may be helpful in understanding the behavior.
There are some other minor differences. For example,
passing --help results in the program returning 1 instead of 0.
https://github.com/google/googletest/issues/3646
PiperOrigin-RevId: 439312700
Change-Id: Id696a25f50f24a5b1785c45ca8fa59794f86fd5c
GoogleTest now follows the Abseil Live at Head philosophy. We recommend using the latest commit in the main branch in your projects.
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.11.0 is now available.
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.
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.
GoogleTest requires a codebase and compiler compliant with the C++11 standard or newer.
The GoogleTest code is officially supported on the following platforms. Operating systems or tools not listed below are community-supported. For community-supported platforms, patches that do not complicate the code may be considered.
If you notice any problems on your platform, please file an issue on the GoogleTest GitHub Issue Tracker. Pull requests containing fixes are welcome!
macOS users: Xcode 9.3+ provides clang 5.0+.
Note: Bazel is the build system used by the team internally and in tests. CMake is supported on a best-effort basis and by the community.
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.
Please read CONTRIBUTING.md for details on how to contribute to this project.
Happy testing!