You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

134 lines
4.6 KiB

  1. # Google Test
  2. #### OSS Builds Status:
  3. [![Build Status](https://api.travis-ci.org/google/googletest.svg?branch=master)](https://travis-ci.org/google/googletest)
  4. [![Build status](https://ci.appveyor.com/api/projects/status/4o38plt0xbo1ubc8/branch/master?svg=true)](https://ci.appveyor.com/project/GoogleTestAppVeyor/googletest/branch/master)
  5. ### Future Plans
  6. #### 1.8.x Release:
  7. [the 1.8.x](https://github.com/google/googletest/releases/tag/release-1.8.1) is
  8. the last release that works with pre-C++11 compilers. The 1.8.x will not accept
  9. any requests for any new features and any bugfix requests will only be accepted
  10. if proven "critical"
  11. #### Post 1.8.x:
  12. On-going work to improve/cleanup/pay technical debt. When this work is completed
  13. there will be a 1.9.x tagged release
  14. #### Post 1.9.x
  15. Post 1.9.x googletest will follow
  16. [Abseil Live at Head philosophy](https://abseil.io/about/philosophy)
  17. ## Welcome to **Google Test**, Google's C++ test framework!
  18. This repository is a merger of the formerly separate GoogleTest and GoogleMock
  19. projects. These were so closely related that it makes sense to maintain and
  20. release them together.
  21. Please subscribe to the mailing list at googletestframework@googlegroups.com for
  22. questions, discussions, and development.
  23. ### Getting started:
  24. The information for **Google Test** is available in the
  25. [Google Test Primer](googletest/docs/primer.md) documentation.
  26. **Google Mock** is an extension to Google Test for writing and using C++ mock
  27. classes. See the separate [Google Mock documentation](googlemock/README.md).
  28. More detailed documentation for googletest is in its interior
  29. [googletest/README.md](googletest/README.md) file.
  30. ## Features
  31. * An [xUnit](https://en.wikipedia.org/wiki/XUnit) test framework.
  32. * Test discovery.
  33. * A rich set of assertions.
  34. * User-defined assertions.
  35. * Death tests.
  36. * Fatal and non-fatal failures.
  37. * Value-parameterized tests.
  38. * Type-parameterized tests.
  39. * Various options for running the tests.
  40. * XML test report generation.
  41. ## Platforms
  42. Google test has been used on a variety of platforms:
  43. * Linux
  44. * Mac OS X
  45. * Windows
  46. * Cygwin
  47. * MinGW
  48. * Windows Mobile
  49. * Symbian
  50. * PlatformIO
  51. ## Who Is Using Google Test?
  52. In addition to many internal projects at Google, Google Test is also used by the
  53. following notable projects:
  54. * The [Chromium projects](http://www.chromium.org/) (behind the Chrome browser
  55. and Chrome OS).
  56. * The [LLVM](http://llvm.org/) compiler.
  57. * [Protocol Buffers](https://github.com/google/protobuf), Google's data
  58. interchange format.
  59. * The [OpenCV](http://opencv.org/) computer vision library.
  60. * [tiny-dnn](https://github.com/tiny-dnn/tiny-dnn): header only,
  61. dependency-free deep learning framework in C++11.
  62. ## Related Open Source Projects
  63. [GTest Runner](https://github.com/nholthaus/gtest-runner) is a Qt5 based
  64. automated test-runner and Graphical User Interface with powerful features for
  65. Windows and Linux platforms.
  66. [Google Test UI](https://github.com/ospector/gtest-gbar) is test runner that
  67. runs your test binary, allows you to track its progress via a progress bar, and
  68. displays a list of test failures. Clicking on one shows failure text. Google
  69. Test UI is written in C#.
  70. [GTest TAP Listener](https://github.com/kinow/gtest-tap-listener) is an event
  71. listener for Google Test that implements the
  72. [TAP protocol](https://en.wikipedia.org/wiki/Test_Anything_Protocol) for test
  73. result output. If your test runner understands TAP, you may find it useful.
  74. [gtest-parallel](https://github.com/google/gtest-parallel) is a test runner that
  75. runs tests from your binary in parallel to provide significant speed-up.
  76. [GoogleTest Adapter](https://marketplace.visualstudio.com/items?itemName=DavidSchuldenfrei.gtest-adapter)
  77. is a VS Code extension allowing to view Google Tests in a tree view, and
  78. run/debug your tests.
  79. ## Requirements
  80. Google Test is designed to have fairly minimal requirements to build and use
  81. with your projects, but there are some. If you notice any problems on your
  82. platform, please notify
  83. [googletestframework@googlegroups.com](https://groups.google.com/forum/#!forum/googletestframework).
  84. Patches for fixing them are welcome!
  85. ### Build Requirements
  86. These are the base requirements to build and use Google Test from a source
  87. package:
  88. * [Bazel](https://bazel.build/) or [CMake](https://cmake.org/). NOTE: Bazel is
  89. the build system that googletest is using internally and tests against.
  90. CMake is community-supported.
  91. * a C++11-standard-compliant compiler
  92. ## Contributing change
  93. Please read the [`CONTRIBUTING.md`](CONTRIBUTING.md) for details on how to
  94. contribute to this project.
  95. Happy testing!