rusefi-full

History

rusefi f8a3d900dc migrating to google test		2019-07-25 00:28:04 -04:00
..
googletest@dea0216d0c	…
test_basic_math	Template-ize bin/value length for interpolation (#878 )	2019-07-09 21:16:36 +03:00
tests	migrating to google test	2019-07-25 00:28:04 -04:00
.cproject	…
.gitignore	…
.project	…
Makefile	reviving unit tests	2019-07-06 21:00:34 -04:00
adc_inputs.h	…
afm2mapConverter.cpp	Template-ize bin/value length for interpolation (#878 )	2019-07-09 21:16:36 +03:00
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	FIRMWARE_ID	2019-07-13 14:08:08 -04:00
map_resize.cpp	…
map_resize.h	…
os_access.h	…
readme.txt	…
rules.mk	…
settings.h	…
test.mk	…
triggers.txt	CBR600 trigger progress	2019-07-23 19:22:40 -04:00
unit_test_framework.cpp	migrating to google test	2019-07-25 00:28:04 -04:00
unit_test_framework.h	migrating to google test	2019-07-25 00:28:04 -04: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 :)