rusefi

History

rusefi 27fb199e66 unit test		2017-11-06 22:33:06 -05:00
..
test_basic_math	better method name	2017-06-11 15:12:41 -04:00
.cproject	…
.gitignore	…
.project	…
Makefile	…
adc_inputs.h	…
boards.cpp	…
boards.h	…
compile.bat	…
efifeatures.h	…
engine_test_helper.cpp	better method name	2017-06-11 15:12:41 -04:00
engine_test_helper.h	…
global.h	…
jenkins.sh	…
junction.exe	…
main.cpp	unit test	2017-11-06 22:33:06 -05:00
main.h	…
makelinks.bat	…
map_resize.cpp	…
map_resize.h	…
readme.txt	…
rules.mk	…
settings.h	…
test.mk	PID auto tune	2017-09-14 07:58:58 -04:00
test_accel_enrichment.cpp	…
test_accel_enrichment.h	…
test_engine_math.cpp	…
test_engine_math.h	…
test_fuel_map.cpp	fixing build	2017-06-11 14:49:23 -04:00
test_fuel_map.h	…
test_idle_controller.cpp	…
test_idle_controller.h	…
test_logic_expression.cpp	cranking_rpm unit test	2017-06-26 08:49:11 +03:00
test_logic_expression.h	…
test_pid_auto.cpp	todo	2017-10-08 18:18:07 -04:00
test_pid_auto.h	PID auto tune	2017-09-14 21:00:28 -04:00
test_sensors.cpp	…
test_sensors.h	…
test_signal_executor.cpp	…
test_signal_executor.h	…
test_speed_density.cpp	refactoring: better method name	2017-11-06 21:48:25 -05:00
test_speed_density.h	…
test_trigger_decoder.cpp	unit test	2017-11-06 22:33:06 -05:00
test_trigger_decoder.h	unit test	2017-11-06 22:33:06 -05:00
test_util.cpp	…
test_util.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 :)