commit | 1800a38fb7d8d4f923fc450875afa3bc16f01151 | [log] [tgz] |
---|---|---|
author | Shahbaz Youssefi <syoussefi@google.com> | Tue Dec 10 10:01:25 2019 -0500 |
committer | Shahbaz Youssefi <syoussefi@chromium.org> | Mon Dec 16 13:01:59 2019 -0500 |
tree | 944119bf036d3169cc2cbfa0c01930d0ee75f362 | |
parent | 4b7809c2f5236b16a2e3b45e2b5ade48fb6a3c0c [diff] |
Revert "Googletest export": disallow empty prefix This reverts commit 20b5b8ecc7a81d23b4716e22a2b35fd53379c8c6. Reason for revert: Breaks existing applications, such as ANGLE (angleproject.org), requires adding an extra prefix that needs to be typed for no reason (when testing from command line) and increases the logs' sizes by a non-trivial amount due to the very large number of tests ANGLE runs. Original commit message: Add a compile time check to ensure that the parameters to TEST_P and INSTANTIATE_TEST_SUITE_P are not empty. Some compilers already fail in that case and, even where it works, it's likely to result in technically invalid code by virtue of creating reserved identifiers: https://en.cppreference.com/w/cpp/language/identifiers First, every project is perfectly capable of adding a prefix if they want to support such a compiler. This change penalizes every project. Second, using a prefix such as `_p` also results in reserved identifiers, so this change is not really solving the problem. For that matter, instead of generating `gtest_##prefix##...`, you can generate `gtest_x##prefix##...` to correctly fix the issue, including when empty prefixes are used.
Release 1.10.x 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.
Please subscribe to the mailing list at googletestframework@googlegroups.com for questions, discussions, and development.
The information for Google Test is available in the Google Test Primer documentation.
Google Mock is an extension to Google Test for writing and using C++ mock classes. See the separate Google Mock documentation.
More detailed documentation for googletest is in its interior googletest/README.md file.
Google test has been used on a variety of platforms:
In addition to many internal projects at Google, Google Test 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.
Google Test UI is 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. Google Test UI is written in C#.
GTest TAP Listener is an event listener for Google Test 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 Google Tests in a tree view, and run/debug your tests.
Catch2 and Google Test Explorer is a VS Code extension allowing to view Google Tests in a tree view, and run/debug your tests.
Cornichon is a small Gherkin DSL parser that generates stub code for Google Test.
Google Test is designed to have fairly minimal requirements to build and use with your projects, but there are some. If you notice any problems on your platform, please notify googletestframework@googlegroups.com. Patches for fixing them are welcome!
These are the base requirements to build and use Google Test from a source package:
Bazel or CMake. NOTE: Bazel is the build system that googletest is using internally and tests against. CMake is community-supported.
a C++11-standard-compliant compiler
Please read the CONTRIBUTING.md
for details on how to contribute to this project.
Happy testing!