Go to file
2018-04-16 15:52:47 -04:00
ci Merges and also adding new bazel build mode 2018-01-31 12:05:18 -05:00
googlemock test-meerging 2018-04-16 15:52:47 -04:00
googletest merging 2018-04-11 13:20:36 -04:00
.gitignore Run autoconf from top-level directory. 2017-12-03 14:07:35 -05:00
.travis.yml Include gcc on mac into PR matrix 2018-04-10 11:28:16 -04:00
appveyor.yml Update appveyor.yml 2018-03-22 11:48:21 -04:00
BUILD.bazel Merges and also adding new bazel build mode 2018-01-31 12:05:18 -05:00
CMakeLists.txt Fix problem installing gtest when gmock enabled 2017-08-16 10:49:06 -04:00
configure.ac Run autoconf from top-level directory. 2017-12-03 14:07:35 -05:00
CONTRIBUTING.md Refactor docs about contributions to CONTRIBUTING.md. 2017-12-11 19:33:27 -05:00
LICENSE Wrong LICENSE file, sorry. Corrected. [skip ci] 2017-12-08 23:16:46 -05:00
Makefile.am Run autoconf from top-level directory. 2017-12-03 14:07:35 -05:00
README.md Update README.md 2018-01-25 10:12:56 -05:00
WORKSPACE Ability to optionally depend on Abseil plus upstream of 183716547 2018-01-30 11:42:03 -05:00

Google Test

Build Status Build status

Welcome to Google Test, 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.

Please see the project page above for more information as well as the mailing list for questions, discussions, and development. There is also an IRC channel on OFTC (irc.oftc.net) #gtest available. Please join us!

Getting started 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 (including build instructions) are in its interior googletest/README.md file.

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.

Platforms

Google test has been used on a variety of platforms:

  • Linux
  • Mac OS X
  • Windows
  • Cygwin
  • MinGW
  • Windows Mobile
  • Symbian

Who Is Using Google Test?

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.

Requirements

Google Test is designed to have fairly minimal requirements to build and use with your projects, but there are some. Currently, we support Linux, Windows, Mac OS X, and Cygwin. We will also make our best effort to support other platforms (e.g. Solaris, AIX, and z/OS). However, since core members of the Google Test project have no access to these platforms, Google Test may have outstanding issues there. If you notice any problems on your platform, please notify googletestframework@googlegroups.com. Patches for fixing them are even more welcome!

Linux Requirements

These are the base requirements to build and use Google Test from a source package (as described below):

  • GNU-compatible Make or gmake
  • POSIX-standard shell
  • POSIX(-2) Regular Expressions (regex.h)
  • A C++98-standard-compliant compiler

Windows Requirements

  • Microsoft Visual C++ 2015 or newer

Cygwin Requirements

  • Cygwin v1.5.25-14 or newer

Mac OS X Requirements

  • Mac OS X v10.4 Tiger or newer
  • Xcode Developer Tools

Contributing change

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

Happy testing!