custom-board-bundle-sample-fork-of-rusefi

History

rusefi 379dd26d69 fresh googletest		2019-01-28 15:49:58 -05:00
..
googletest@4fe76c4d6e	fresh googletest	2019-01-28 15:49:58 -05:00
test_basic_math	…
tests	#657 pulling global access down	2019-01-28 00:44:30 -05:00
.cproject	…
.gitignore	…
.project	…
Makefile	trying ideas about testability	2019-01-17 00:24:41 -05:00
adc_inputs.h	…
afm2mapConverter.cpp	…
afm2mapConverter.h	…
boards.cpp	…
boards.h	…
compile.bat	…
efifeatures.h	…
engine_test_helper.cpp	unit tests framework fix	2019-01-22 23:09:34 -05:00
engine_test_helper.h	testing API improvement (?)	2019-01-21 22:34:17 -05:00
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	trying ideas about testability	2019-01-17 00:24:41 -05:00
map_resize.cpp	…
map_resize.h	…
readme.txt	…
rules.mk	…
settings.h	…
test.mk	trying ideas about testability	2019-01-17 00:24:41 -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 :)