This repository has been archived by the owner on Nov 6, 2020. It is now read-only.
forked from ros/urdfdom
-
Notifications
You must be signed in to change notification settings - Fork 5
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
gtest: new version to fix warnings (#9)
- Loading branch information
1 parent
7763c64
commit 70a48ec
Showing
37 changed files
with
3,822 additions
and
1,428 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,157 @@ | ||
Changes for 1.7.0: | ||
|
||
* New feature: death tests are supported on OpenBSD and in iOS | ||
simulator now. | ||
* New feature: Google Test now implements a protocol to allow | ||
a test runner to detect that a test program has exited | ||
prematurely and report it as a failure (before it would be | ||
falsely reported as a success if the exit code is 0). | ||
* New feature: Test::RecordProperty() can now be used outside of the | ||
lifespan of a test method, in which case it will be attributed to | ||
the current test case or the test program in the XML report. | ||
* New feature (potentially breaking): --gtest_list_tests now prints | ||
the type parameters and value parameters for each test. | ||
* Improvement: char pointers and char arrays are now escaped properly | ||
in failure messages. | ||
* Improvement: failure summary in XML reports now includes file and | ||
line information. | ||
* Improvement: the <testsuites> XML element now has a timestamp attribute. | ||
* Improvement: When --gtest_filter is specified, XML report now doesn't | ||
contain information about tests that are filtered out. | ||
* Fixed the bug where long --gtest_filter flag values are truncated in | ||
death tests. | ||
* Potentially breaking change: RUN_ALL_TESTS() is now implemented as a | ||
function instead of a macro in order to work better with Clang. | ||
* Compatibility fixes with C++ 11 and various platforms. | ||
* Bug/warning fixes. | ||
|
||
Changes for 1.6.0: | ||
|
||
* New feature: ADD_FAILURE_AT() for reporting a test failure at the | ||
given source location -- useful for writing testing utilities. | ||
* New feature: the universal value printer is moved from Google Mock | ||
to Google Test. | ||
* New feature: type parameters and value parameters are reported in | ||
the XML report now. | ||
* A gtest_disable_pthreads CMake option. | ||
* Colored output works in GNU Screen sessions now. | ||
* Parameters of value-parameterized tests are now printed in the | ||
textual output. | ||
* Failures from ad hoc test assertions run before RUN_ALL_TESTS() are | ||
now correctly reported. | ||
* Arguments of ASSERT_XY and EXPECT_XY no longer need to support << to | ||
ostream. | ||
* More complete handling of exceptions. | ||
* GTEST_ASSERT_XY can be used instead of ASSERT_XY in case the latter | ||
name is already used by another library. | ||
* --gtest_catch_exceptions is now true by default, allowing a test | ||
program to continue after an exception is thrown. | ||
* Value-parameterized test fixtures can now derive from Test and | ||
WithParamInterface<T> separately, easing conversion of legacy tests. | ||
* Death test messages are clearly marked to make them more | ||
distinguishable from other messages. | ||
* Compatibility fixes for Android, Google Native Client, MinGW, HP UX, | ||
PowerPC, Lucid autotools, libCStd, Sun C++, Borland C++ Builder (Code Gear), | ||
IBM XL C++ (Visual Age C++), and C++0x. | ||
* Bug fixes and implementation clean-ups. | ||
* Potentially incompatible changes: disables the harmful 'make install' | ||
command in autotools. | ||
|
||
Changes for 1.5.0: | ||
|
||
* New feature: assertions can be safely called in multiple threads | ||
where the pthreads library is available. | ||
* New feature: predicates used inside EXPECT_TRUE() and friends | ||
can now generate custom failure messages. | ||
* New feature: Google Test can now be compiled as a DLL. | ||
* New feature: fused source files are included. | ||
* New feature: prints help when encountering unrecognized Google Test flags. | ||
* Experimental feature: CMake build script (requires CMake 2.6.4+). | ||
* Experimental feature: the Pump script for meta programming. | ||
* double values streamed to an assertion are printed with enough precision | ||
to differentiate any two different values. | ||
* Google Test now works on Solaris and AIX. | ||
* Build and test script improvements. | ||
* Bug fixes and implementation clean-ups. | ||
|
||
Potentially breaking changes: | ||
|
||
* Stopped supporting VC++ 7.1 with exceptions disabled. | ||
* Dropped support for 'make install'. | ||
|
||
Changes for 1.4.0: | ||
|
||
* New feature: the event listener API | ||
* New feature: test shuffling | ||
* New feature: the XML report format is closer to junitreport and can | ||
be parsed by Hudson now. | ||
* New feature: when a test runs under Visual Studio, its failures are | ||
integrated in the IDE. | ||
* New feature: /MD(d) versions of VC++ projects. | ||
* New feature: elapsed time for the tests is printed by default. | ||
* New feature: comes with a TR1 tuple implementation such that Boost | ||
is no longer needed for Combine(). | ||
* New feature: EXPECT_DEATH_IF_SUPPORTED macro and friends. | ||
* New feature: the Xcode project can now produce static gtest | ||
libraries in addition to a framework. | ||
* Compatibility fixes for Solaris, Cygwin, minGW, Windows Mobile, | ||
Symbian, gcc, and C++Builder. | ||
* Bug fixes and implementation clean-ups. | ||
|
||
Changes for 1.3.0: | ||
|
||
* New feature: death tests on Windows, Cygwin, and Mac. | ||
* New feature: ability to use Google Test assertions in other testing | ||
frameworks. | ||
* New feature: ability to run disabled test via | ||
--gtest_also_run_disabled_tests. | ||
* New feature: the --help flag for printing the usage. | ||
* New feature: access to Google Test flag values in user code. | ||
* New feature: a script that packs Google Test into one .h and one | ||
.cc file for easy deployment. | ||
* New feature: support for distributing test functions to multiple | ||
machines (requires support from the test runner). | ||
* Bug fixes and implementation clean-ups. | ||
|
||
Changes for 1.2.1: | ||
|
||
* Compatibility fixes for Linux IA-64 and IBM z/OS. | ||
* Added support for using Boost and other TR1 implementations. | ||
* Changes to the build scripts to support upcoming release of Google C++ | ||
Mocking Framework. | ||
* Added Makefile to the distribution package. | ||
* Improved build instructions in README. | ||
|
||
Changes for 1.2.0: | ||
|
||
* New feature: value-parameterized tests. | ||
* New feature: the ASSERT/EXPECT_(NON)FATAL_FAILURE(_ON_ALL_THREADS) | ||
macros. | ||
* Changed the XML report format to match JUnit/Ant's. | ||
* Added tests to the Xcode project. | ||
* Added scons/SConscript for building with SCons. | ||
* Added src/gtest-all.cc for building Google Test from a single file. | ||
* Fixed compatibility with Solaris and z/OS. | ||
* Enabled running Python tests on systems with python 2.3 installed, | ||
e.g. Mac OS X 10.4. | ||
* Bug fixes. | ||
|
||
Changes for 1.1.0: | ||
|
||
* New feature: type-parameterized tests. | ||
* New feature: exception assertions. | ||
* New feature: printing elapsed time of tests. | ||
* Improved the robustness of death tests. | ||
* Added an Xcode project and samples. | ||
* Adjusted the output format on Windows to be understandable by Visual Studio. | ||
* Minor bug fixes. | ||
|
||
Changes for 1.0.1: | ||
|
||
* Added project files for Visual Studio 7.1. | ||
* Fixed issues with compiling on Mac OS X. | ||
* Fixed issues with compiling on Cygwin. | ||
|
||
Changes for 1.0.0: | ||
|
||
* Initial Open Source release of Google Test |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,37 @@ | ||
# This file contains a list of people who've made non-trivial | ||
# contribution to the Google C++ Testing Framework project. People | ||
# who commit code to the project are encouraged to add their names | ||
# here. Please keep the list sorted by first names. | ||
|
||
Ajay Joshi <[email protected]> | ||
Balázs Dán <[email protected]> | ||
Bharat Mediratta <[email protected]> | ||
Chandler Carruth <[email protected]> | ||
Chris Prince <[email protected]> | ||
Chris Taylor <[email protected]> | ||
Dan Egnor <[email protected]> | ||
Eric Roman <[email protected]> | ||
Hady Zalek <[email protected]> | ||
Jeffrey Yasskin <[email protected]> | ||
Jói Sigurðsson <[email protected]> | ||
Keir Mierle <[email protected]> | ||
Keith Ray <[email protected]> | ||
Kenton Varda <[email protected]> | ||
Manuel Klimek <[email protected]> | ||
Markus Heule <[email protected]> | ||
Mika Raento <[email protected]> | ||
Miklós Fazekas <[email protected]> | ||
Pasi Valminen <[email protected]> | ||
Patrick Hanna <[email protected]> | ||
Patrick Riley <[email protected]> | ||
Peter Kaminski <[email protected]> | ||
Preston Jackson <[email protected]> | ||
Rainer Klaffenboeck <[email protected]> | ||
Russ Cox <[email protected]> | ||
Russ Rufer <[email protected]> | ||
Sean Mcafee <[email protected]> | ||
Sigurður Ásgeirsson <[email protected]> | ||
Tracy Bialik <[email protected]> | ||
Vadim Berman <[email protected]> | ||
Vlad Losev <[email protected]> | ||
Zhanyong Wan <[email protected]> |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,28 @@ | ||
Copyright 2008, Google Inc. | ||
All rights reserved. | ||
|
||
Redistribution and use in source and binary forms, with or without | ||
modification, are permitted provided that the following conditions are | ||
met: | ||
|
||
* Redistributions of source code must retain the above copyright | ||
notice, this list of conditions and the following disclaimer. | ||
* Redistributions in binary form must reproduce the above | ||
copyright notice, this list of conditions and the following disclaimer | ||
in the documentation and/or other materials provided with the | ||
distribution. | ||
* Neither the name of Google Inc. nor the names of its | ||
contributors may be used to endorse or promote products derived from | ||
this software without specific prior written permission. | ||
|
||
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS | ||
"AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT | ||
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR | ||
A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT | ||
OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, | ||
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT | ||
LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, | ||
DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY | ||
THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT | ||
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE | ||
OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.