rusefi-1

History

rusefi 37a9e66bc1 Annotations in C++ code to produce formulas in rusEfi console #807		2019-06-19 22:34:11 -04:00
..
googletest@dea0216d0c	fresh googletest	2019-06-02 14:56:32 -04:00
test_basic_math	migrating to googletest	2019-01-14 18:38:20 -05:00
tests	Annotations in C++ code to produce formulas in rusEfi console #807	2019-06-19 22:34:11 -04:00
.cproject	…
.gitignore	…
.project	…
Makefile	MK clean-up	2019-06-15 16:43:30 -04:00
adc_inputs.h	…
afm2mapConverter.cpp	…
afm2mapConverter.h	…
boards.cpp	#699	2019-02-28 21:09:31 -05:00
boards.h	#699	2019-02-28 21:09:31 -05:00
compile.bat	ooooops I forgot about Jenkins settings!	2019-01-12 21:15:05 -05:00
efifeatures.h	More compatibility for ADC_inputs, etc. (#716 )	2019-03-28 22:46:10 -04:00
engine_test_helper.cpp	reducing code duplication with unit tests	2019-05-12 20:24:35 -04:00
engine_test_helper.h	BUG: phase sensor validation attending - detect missing CAM signal #659	2019-05-10 21:56:33 -04:00
global.h	refactoring: reducing code duplication	2019-02-23 12:33:49 -05:00
global_execution_queue.cpp	random cleanup	2019-04-15 19:24:46 -04:00
global_execution_queue.h	random cleanup	2019-04-15 19:24:46 -04:00
globalaccess.h	#657	2019-01-28 02:59:14 -05:00
gmock-all.cpp	#35 first unit test with a mock!	2019-01-08 01:20:18 -05:00
gtest-all.cpp	…
jenkins.sh	…
main.cpp	Trigger: warning code on normal engine start up #669	2019-05-10 22:55:08 -04:00
map_resize.cpp	migrating to googletest	2019-01-14 15:45:35 -05:00
map_resize.h	…
readme.txt	…
rules.mk	…
settings.h	…
test.mk	MK clean-up	2019-06-15 16:43:30 -04:00
triggers.txt	different precision with different bitness in compiler?	2019-01-12 15:03:41 -05:00
unit_test_framework.cpp	migrating to googletest	2019-01-14 23:40:13 -05:00
unit_test_framework.h	migrating to googletest	2019-01-14 23:40:13 -05:00

readme.txt

In this folder we have a naive test suite.

I am not sure what is the best approach to tests in C (someone can educate me), but my approach is:

Unit tests are not aware of ChibiOS or ARM or else, they are just plain C/C++ which you build for your desktop, not your MCU.

Run 'make' to build desktop binary & run it on your PC/Mac, it's expected to say SUCCESS and not fail :)