rusefi-1/unit_tests
rusEfi 1070520d7d auto-sync 2017-01-19 17:04:15 -05:00
..
test_basic_math auto-sync 2017-01-03 14:05:36 -05:00
test_data_structures auto-sync 2017-01-03 14:05:36 -05:00
.cproject auto-sync 2017-01-02 19:03:36 -05:00
.project
Makefile auto-sync 2017-01-19 17:04:15 -05:00
adc_inputs.h auto-sync 2017-01-03 06:05:22 -05:00
boards.cpp auto-sync 2017-01-03 06:05:22 -05:00
boards.h
compile.bat
efifeatures.h auto-sync 2017-01-06 11:02:49 -05:00
engine_test_helper.cpp auto-sync 2016-12-18 12:03:48 -05:00
engine_test_helper.h auto-sync 2016-12-18 12:03:48 -05:00
global.h auto-sync 2016-11-03 23:02:58 -04:00
jenkins.sh
junction.exe
main.cpp auto-sync 2017-01-02 15:03:26 -05:00
main.h auto-sync 2016-09-03 12:03:10 -04:00
makelinks.bat auto-sync 2017-01-02 14:03:17 -05:00
map_resize.cpp auto-sync 2017-01-03 14:05:36 -05:00
map_resize.h auto-sync 2017-01-03 14:05:36 -05:00
readme.txt
rules.mk
settings.h
test.mk
test_accel_enrichment.cpp auto-sync 2016-11-30 21:06:24 -05:00
test_accel_enrichment.h
test_engine_math.cpp auto-sync 2016-10-11 21:03:00 -04:00
test_engine_math.h
test_fuel_map.cpp auto-sync 2017-01-05 21:12:06 -05:00
test_fuel_map.h
test_idle_controller.cpp auto-sync 2016-12-26 15:03:03 -05:00
test_idle_controller.h
test_logic_expression.cpp auto-sync 2016-10-10 14:02:17 -04:00
test_logic_expression.h
test_sensors.cpp auto-sync 2017-01-03 14:05:36 -05:00
test_sensors.h auto-sync 2017-01-03 14:05:36 -05:00
test_signal_executor.cpp auto-sync 2017-01-03 14:05:36 -05:00
test_signal_executor.h auto-sync 2017-01-03 14:05:36 -05:00
test_speed_density.cpp auto-sync 2016-08-27 10:03:11 -04:00
test_speed_density.h
test_trigger_decoder.cpp auto-sync 2017-01-03 17:01:42 -05:00
test_trigger_decoder.h auto-sync 2017-01-03 14:05:36 -05:00
test_util.cpp auto-sync 2017-01-03 14:05:36 -05:00
test_util.h auto-sync 2017-01-03 14:05:36 -05:00

readme.txt

In this folder we have a naive test set. I am not sure what is the best approach to tests in C (someone can educate me), but my approach is:

1) with a symlink linking some (only some, not all) folders of the firmware implementation, we can compile some files of the firmware as win32 code.
Please execute the 'makelinks.bat' file to get the links. On XP you might need to execute 'junction.exe' before exuting the .bat file.

2) we then compile & run the .exe, which is expected to say SUCCESS and not fail :)