Mickey Rose 78756a9056 better tests for logical expressions ... Two of the original checks were not testing what they were supposed to test, because the result of eval didn't depend on correct parsing: eval("not true or not true") correct parse: ((not true) or (not true)) == false incorrect parse: (not (true or (not true))) == false eval("not false and not false") correct parse: ((not false) and (not false)) == true incorrect parse: (not (false and (not false))) == true (cherry picked from commit d38d16ade9)		2020-01-02 19:32:12 +01:00
..
data@b4aa4c462f	Update tests	2018-10-23 19:54:26 +00:00
data-visual@6a1af6c24b	Update visual tests	2018-11-29 17:57:35 +00:00
standalone	freetype_engine : revert back to original APIs usage.	2017-06-01 12:35:14 +02:00
unit	better tests for logical expressions	2020-01-02 19:32:12 +01:00
visual	visual tests: report failed tests (#3765)	2018-01-24 15:39:13 +00:00
build.py	clean up test binaries if not building them again [skip ci]	2016-03-11 17:52:07 -08:00
catch.hpp	add custom command line options to unit tests - refs philsquared/Catch#381	2016-01-05 17:13:36 -08:00
catch_ext.hpp	expressions test: move expression strings into Catch calls, continue on failure	2016-02-05 17:22:01 +01:00
cleanup.hpp	more warning_ignore usage - refs #2907	2016-03-09 16:43:00 -08:00
run	Fix unbound variable when number of JOBS is omitted	2016-06-23 09:46:45 +01:00