custom-board-bundle-sample-.../unit_tests
rusefi 8303dc7595 refactoring: no logic changes, just nicer variable and method names 2019-03-12 18:54:46 -04:00
..
googletest@4fe76c4d6e
test_basic_math
tests refactoring: no logic changes, just nicer variable and method names 2019-03-12 18:54:46 -04:00
.cproject
.gitignore
.project
Makefile
adc_inputs.h
afm2mapConverter.cpp
afm2mapConverter.h
boards.cpp
boards.h
compile.bat
efifeatures.h
engine_test_helper.cpp
engine_test_helper.h
global.h
global_execution_queue.cpp
global_execution_queue.h
globalaccess.h
gmock-all.cpp
gtest-all.cpp
jenkins.sh
main.cpp
map_resize.cpp
map_resize.h
readme.txt
rules.mk
settings.h
test.mk
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 :)