fome-fw/unit_tests
rusefi fe5db79edb fixed #363 2017-03-04 20:52:24 -05:00
..
test_basic_math auto-sync 2017-01-03 14:05:36 -05:00
test_data_structures removing dead code 2017-03-01 21:14:41 -05:00
.cproject relative paths 2017-02-21 11:16:40 -05:00
.project
Makefile auto-sync 2017-01-19 17:04:15 -05:00
adc_inputs.h
boards.cpp
boards.h
compile.bat auto-sync 2017-02-17 01:01:43 -05:00
efifeatures.h auto-sync 2017-01-06 11:02:49 -05:00
engine_test_helper.cpp progress #363 2017-03-01 22:18:25 -05:00
engine_test_helper.h
global.h progress #363 2017-03-01 22:18:25 -05:00
jenkins.sh
junction.exe
main.cpp better method name & docs 2017-03-04 09:13:08 -05:00
main.h better method name & docs 2017-03-04 09:13:08 -05:00
makelinks.bat
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
test_accel_enrichment.h
test_engine_math.cpp
test_engine_math.h
test_fuel_map.cpp progress #363 2017-03-01 22:18:25 -05:00
test_fuel_map.h
test_idle_controller.cpp
test_idle_controller.h
test_logic_expression.cpp
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
test_speed_density.h
test_trigger_decoder.cpp fixed #363 2017-03-04 20:52:24 -05:00
test_trigger_decoder.h progress #363 2017-03-04 00:00:46 -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 :)