rusefi-1

History

rusefi 39663a60d2 fresh modules		2019-02-21 06:10:38 -05:00
..
googletest@4fe76c4d6e	fresh modules	2019-02-21 06:10:38 -05:00
test_basic_math	…
tests	better (?) variable names	2019-02-10 22:47:49 -05:00
.cproject	…
.gitignore	…
.project	…
Makefile	Migrate to Chibios 18 stable #631	2019-02-03 21:19:26 -05:00
adc_inputs.h	…
afm2mapConverter.cpp	…
afm2mapConverter.h	…
boards.cpp	…
boards.h	…
compile.bat	…
efifeatures.h	…
engine_test_helper.cpp	refactoring: reducing code duplication	2019-02-03 09:20:36 -05:00
engine_test_helper.h	…
global.h	#657	2019-01-28 02:59:14 -05:00
global_execution_queue.cpp	…
global_execution_queue.h	…
globalaccess.h	#657	2019-01-28 02:59:14 -05:00
gmock-all.cpp	…
gtest-all.cpp	…
jenkins.sh	…
main.cpp	Migrate to Chibios 18 stable #631	2019-02-03 21:19:26 -05:00
map_resize.cpp	…
map_resize.h	…
readme.txt	…
rules.mk	…
settings.h	…
test.mk	Multiple sync pattern for faster cranking #679	2019-02-03 00:50:10 -05:00
triggers.txt	…
unit_test_framework.cpp	…
unit_test_framework.h	…

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 :)