fome-fw

History

rusefi 8d8d3c32ca better folder structure		2019-01-05 21:49:47 -05:00
..
googletest@542e057c6c	googletest	2019-01-03 18:37:12 -05:00
test_basic_math	docs	2018-12-08 11:08:41 -05:00
tests	better folder structure	2019-01-05 21:49:47 -05:00
.cproject	enabling parallel compilation from Eclipse	2019-01-04 00:18:08 -05:00
.gitignore	trigger image progress	2018-02-28 23:31:58 -05:00
.project	…
Makefile	better folder structure	2019-01-05 21:49:47 -05:00
adc_inputs.h	…
afm2mapConverter.cpp	#538	2018-01-21 16:11:39 -05:00
afm2mapConverter.h	…
boards.cpp	…
boards.h	…
compile.bat	…
efifeatures.h	#617	2019-01-03 07:22:21 -05:00
engine_test_helper.cpp	making either Matt or compiler or both happier	2019-01-05 00:11:17 -05:00
engine_test_helper.h	refactoring	2018-07-28 19:51:41 -04:00
global.h	making either Matt or compiler or both happier	2019-01-05 00:11:17 -05:00
global_execution_queue.cpp	reducing clutter	2018-12-08 18:11:28 -05:00
gtest-all.cpp	googletest	2019-01-03 20:14:23 -05:00
jenkins.sh	…
main.cpp	googletest	2019-01-03 20:14:23 -05:00
map_resize.cpp	refactoring	2018-09-16 23:10:06 -04:00
map_resize.h	…
readme.txt	…
rules.mk	…
settings.h	…
test.mk	better folder structure	2019-01-05 21:49:47 -05:00
triggers.txt	more docs related to trigger process	2018-11-22 10:25:02 -05:00
unit_test_framework.cpp	refactoring	2018-09-16 22:39:46 -04:00
unit_test_framework.h	progress	2018-03-04 23:42:30 -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 :)