fome-fw

History

rusefi 5eec063b7f fresh googletest		2019-06-02 14:56:32 -04:00
..
googletest@dea0216d0c	fresh googletest	2019-06-02 14:56:32 -04:00
test_basic_math	…
tests	progress & fixinig unit tests	2019-06-01 09:11:01 -04:00
.cproject	…
.gitignore	…
.project	…
Makefile	Try ccache #769	2019-04-20 21:44:00 -04:00
adc_inputs.h	…
afm2mapConverter.cpp	…
afm2mapConverter.h	…
boards.cpp	…
boards.h	…
compile.bat	…
efifeatures.h	…
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	…
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	…
gmock-all.cpp	…
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	…
map_resize.h	…
readme.txt	…
rules.mk	…
settings.h	…
test.mk	Multiple sync pattern for faster cranking #679	2019-05-12 19:58:15 -04: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 :)