fome-fw

History

rusefi 8e0e034468 different precision with different bitness in compiler?		2019-01-12 15:03:41 -05:00
..
googletest@542e057c6c	…
test_basic_math	minor fix	2019-01-08 23:02:04 -05:00
tests	cyclic_buffer.contains method	2019-01-12 14:01:13 -05:00
.cproject	…
.gitignore	…
.project	…
Makefile	windows unit tests are now 64 bit	2019-01-12 14:31:55 -05:00
adc_inputs.h	…
afm2mapConverter.cpp	…
afm2mapConverter.h	…
boards.cpp	…
boards.h	…
compile.bat	…
efifeatures.h	#655 clean-up	2019-01-09 00:25:45 -05:00
engine_test_helper.cpp	making warning codes more unit testable	2019-01-12 08:34:38 -05:00
engine_test_helper.h	reducing global variables in tests	2019-01-10 21:50:13 -05:00
global.h	new unit test	2019-01-11 19:08:15 -05:00
global_execution_queue.cpp	The Big Refactoring of 2019: scheduler should not be global #655	2019-01-09 20:06:41 -05:00
global_execution_queue.h	The Big Refactoring of 2019: scheduler should not be global #655	2019-01-09 20:06:41 -05:00
gmock-all.cpp	#35 first unit test with a mock!	2019-01-08 01:20:18 -05:00
gtest-all.cpp	…
jenkins.sh	…
main.cpp	reducing global variables in tests	2019-01-10 23:24:36 -05:00
map_resize.cpp	…
map_resize.h	…
readme.txt	…
rules.mk	…
settings.h	…
test.mk	Improve wall wetting AE to use time constant (#650 )	2019-01-06 20:45:51 -05:00
triggers.txt	different precision with different bitness in compiler?	2019-01-12 15:03:41 -05:00
unit_test_framework.cpp	…
unit_test_framework.h	reducing global variables in tests	2019-01-10 23:09:56 -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 :)