anon a303e08859 Option to omit UnityBegin/UnityEnd calls in generate_test_runner ... By passing --omit_begin_end=1 to generate_test_runner.rb, the script will now omit calls to UnityBegin and UnityEnd when running tests in a suite. This allows multiple suites to be executed in a row, and then have an overall summary of the tests which were executed across all suites.		2019-10-29 20:32:06 +00:00
..
colour_prompt.rb	Updated to newer coding standard	2019-10-24 15:33:41 -04:00
colour_reporter.rb	Fix (most) Rubocop warnings.	2018-11-28 13:27:00 -05:00
generate_config.yml	More fixes to line endings	2016-01-07 14:20:59 -05:00
generate_module.rb	Updated to newer coding standard	2019-10-24 15:33:41 -04:00
generate_test_runner.rb	Option to omit UnityBegin/UnityEnd calls in generate_test_runner	2019-10-29 20:32:06 +00:00
parse_output.rb	Updated to newer coding standard	2019-10-24 15:33:41 -04:00
run_test.erb	Convert RUN_TEST() to a function (generated from an ERB template).	2019-10-22 15:18:20 -04:00
stylize_as_junit.rb	Updated to newer coding standard	2019-10-24 15:33:41 -04:00
test_file_filter.rb	Fix (most) Rubocop warnings.	2018-11-28 13:27:00 -05:00
type_sanitizer.rb	Starting to enforce our coding style. The first step is that we’ve pulled in Rubocop to check out Ruby syntax. There is likely a bit of customization to do yet AND there is definitely that backlog of todo’s that we just told it to ignore.	2017-03-28 08:44:32 -04:00
unity_test_summary.py	recursive search for target test files in test summary python script	2019-03-26 17:32:30 +02:00
unity_test_summary.rb	Updated to newer coding standard	2019-10-24 15:33:41 -04:00
unity_to_junit.py	add unity_to_junit.py	2016-06-21 09:43:26 +02:00