Simon Gene Gottlieb f2608bf2f1 adjusting test to use stable floating point numbers ... The issue is that numbers like 2.01 or 3.01 can not be precisely represented with binary floating point numbers. This is implemented in foresight, that fixing floating points in yaml-cpp will break these unittests, even though they shouldn't.		2018-12-11 22:16:34 +01:00
..
gtest-1.8.0	test: Upgrade googlemock 1.7.0 to googletest 1.8.0	2017-08-24 22:49:17 -05:00
integration	adjusting test to use stable floating point numbers	2018-12-11 22:16:34 +01:00
node	adjusting test to use stable floating point numbers	2018-12-11 22:16:34 +01:00
CMakeLists.txt	Improvements to CMake buildsystem	2018-09-03 10:37:06 -05:00
create-emitter-tests.py	Add EmitterStyle, which will allow sequence or map style (i.e., flow or block) to be preserved between parsing and emitting	2015-01-24 12:19:20 -06:00
handler_test.h	Factored out HandlerTest as a base class	2014-03-23 16:26:44 -05:00
main.cpp	Convert node tests to gtest	2014-03-23 19:21:13 -05:00
mock_event_handler.h	Add EmitterStyle, which will allow sequence or map style (i.e., flow or block) to be preserved between parsing and emitting	2015-01-24 12:19:20 -06:00
ostream_wrapper_test.cpp	Run IWYU	2014-03-22 22:46:04 -05:00
regex_test.cpp	add some tests for RegEx	2016-03-26 14:52:11 -04:00
specexamples.h	Convert spec tests to gtest with gmock	2014-03-23 12:49:30 -05:00