rusefi-full/unit_tests
rusEfi 38b3771a4b auto-sync 2016-07-13 21:03:05 -04:00
..
test_basic_math
test_data_structures
.cproject
.project
Makefile auto-sync 2016-07-01 18:03:23 -04:00
adc_inputs.h
boards.cpp
boards.h
compile.bat
efifeatures.h
engine_test_helper.cpp
engine_test_helper.h
global.h
jenkins.sh
junction.exe
main.cpp
main.h
makelinks.bat
map_resize.cpp
map_resize.h
readme.txt
rules.mk
settings.h
test.mk
test_accel_enrichment.cpp
test_accel_enrichment.h
test_engine_math.cpp auto-sync 2016-07-01 19:01:44 -04:00
test_engine_math.h
test_fuel_map.cpp auto-sync 2016-07-01 19:01:44 -04:00
test_fuel_map.h
test_idle_controller.cpp auto-sync 2016-07-13 21:03:05 -04:00
test_idle_controller.h
test_logic_expression.cpp
test_logic_expression.h
test_sensors.cpp
test_sensors.h
test_signal_executor.cpp
test_signal_executor.h
test_speed_density.cpp
test_speed_density.h
test_trigger_decoder.cpp
test_trigger_decoder.h
test_util.cpp
test_util.h

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 :)