fome-fw

History

rusefi 141e392a05 refactoring: reducing header tree hell		2019-01-20 23:44:05 -05:00
..
googletest@542e057c6c	…
test_basic_math	migrating to googletest	2019-01-14 18:38:20 -05:00
tests	future fast spinning 60/2 test	2019-01-20 22:21:12 -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	Question: something strange trigger errors #662	2019-01-12 15:32:40 -05:00
boards.h	Question: something strange trigger errors #662	2019-01-12 15:32:40 -05:00
compile.bat	ooooops I forgot about Jenkins settings!	2019-01-12 21:15:05 -05:00
efifeatures.h	…
engine_test_helper.cpp	future fast spinning 60/2 test	2019-01-20 22:21:12 -05:00
engine_test_helper.h	future fast spinning 60/2 test	2019-01-20 22:21:12 -05:00
global.h	refactoring: reducing header tree hell	2019-01-20 23:44:05 -05:00
global_execution_queue.cpp	…
global_execution_queue.h	…
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	migrating to googletest	2019-01-14 15:45:35 -05:00
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	different precision with different bitness in compiler?	2019-01-12 15:03:41 -05:00
unit_test_framework.cpp	migrating to googletest	2019-01-14 23:40:13 -05:00
unit_test_framework.h	migrating to googletest	2019-01-14 23:40:13 -05: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 :)