Mickey Rose d38d16ade9 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		2020-01-02 17:30:24 +01:00
..
data@c3982b7660	update dependencies	2018-11-20 14:36:59 +00:00
data-visual@901ee22d4c	Update visual tests	2019-05-17 22:55:42 +02:00
standalone	remove unused code	2018-06-26 15:57:21 -07:00
unit	better tests for logical expressions	2020-01-02 17:30:24 +01:00
visual	Cairo: set version of SVG to 1.2	2019-02-08 12:32:01 +00:00
build.py	make ScriptRun class visible	2019-11-06 15:08:30 +00: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