commit | e1a38bc3707741d249fa22d2064552a08e37555b | [log] [tgz] |
---|---|---|
author | Abseil Team <absl-team@google.com> | Thu Mar 07 23:53:04 2024 -0800 |
committer | Copybara-Service <copybara-worker@google.com> | Thu Mar 07 23:53:47 2024 -0800 |
tree | 596321a4fa5a9329f510e8972a22d42d9590aa7a | |
parent | 31993dfa6b47e11c7a6ef67cfa8af90892b9bd1c [diff] |
Reland: Optimize Google Test process startup Google Test performs hidden test registration during process startup. For test binaries that contain a large number of tests, this registration can be costly. In this CL, we reduce the overhead of registration via several tactics: - Treat CodeLocation and FilePath as value types, using std::move to pass them around. - Reduce string copies in various places by either passing std::string values via std::move, or passing const-refs to std::string instances. - Use std::to_string to stringify an int in DefaultParamName rather than a std::stringstream. - Pull some std::string instances out of nested loops in ParameterizedTestSuiteInfo::RegisterTests so as to reuse some allocations, and replace stringstream with ordinary string appends. - Use std::unordered_map in UnitTestImpl::GetTestSuite and ParameterizedTestSuiteRegistry::GetTestSuitePatternHolder to spend a little memory to turn O(N) lookups into constant time lookpus. - Use range-based for loops in a few places. - Use emplace-ish methods to add to containers where appropriate. All together, these changes reduce the overall runtime of a series of 50 death tests in a single Chromium test executable by ~38% due to the fact that the registration costs are paid in every death test's child process. PiperOrigin-RevId: 613833210 Change-Id: I51a262a770edff98ffa1e3b60c4d78a8308f9a9f
GoogleTest now follows the Abseil Live at Head philosophy. We recommend updating to the latest commit in the main
branch as often as possible. We do publish occasional semantic versions, tagged with v${major}.${minor}.${patch}
(e.g. v1.14.0
).
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.14.0 is now available.
The 1.14.x branch requires at least C++14.
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.
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 follows Google's Foundational C++ Support Policy. See this table for a list of currently supported versions of compilers, platforms, and build tools.
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!