rusefi

History

dron0gus a122451301 unit test compilation fix under linux (#747 )		2019-04-12 22:08:52 +02:00
..
googletest@4fe76c4d6e	fresh modules	2019-02-21 06:10:38 -05:00
test_basic_math	…
tests	unit test compilation fix under linux (#747 )	2019-04-12 22:08:52 +02:00
.cproject	…
.gitignore	…
.project	…
Makefile	The Big Refactoring of 2019: folder structure #723	2019-04-09 23:01:45 -04:00
adc_inputs.h	…
afm2mapConverter.cpp	…
afm2mapConverter.h	…
boards.cpp	#699	2019-02-28 21:09:31 -05:00
boards.h	#699	2019-02-28 21:09:31 -05:00
compile.bat	…
efifeatures.h	More compatibility for ADC_inputs, etc. (#716 )	2019-03-28 22:46:10 -04:00
engine_test_helper.cpp	docs	2019-03-04 00:14:55 -05:00
engine_test_helper.h	…
global.h	refactoring: reducing code duplication	2019-02-23 12:33:49 -05:00
global_execution_queue.cpp	fix #698	2019-02-27 17:12:52 -05:00
global_execution_queue.h	…
globalaccess.h	…
gmock-all.cpp	…
gtest-all.cpp	…
jenkins.sh	…
main.cpp	Migrate to Chibios 18 stable #631	2019-02-03 21:19:26 -05:00
map_resize.cpp	…
map_resize.h	…
readme.txt	…
rules.mk	…
settings.h	…
test.mk	gpiochips API, core and unit test (#703 )	2019-03-12 10:12:37 -04:00
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 :)