fome-fw

History

rusEfi 3e7cbbefe8 auto-sync		2016-03-15 22:03:43 -04:00
..
test_basic_math	…
test_data_structures	…
.cproject	…
.project	…
Makefile	auto-sync	2016-02-12 11:02:09 -05:00
adc_inputs.h	…
boards.cpp	…
boards.h	…
compile.bat	…
efifeatures.h	…
engine_test_helper.cpp	auto-sync	2016-03-11 11:03:18 -05:00
engine_test_helper.h	…
global.h	…
jenkins.sh	…
junction.exe	…
main.cpp	auto-sync	2016-01-26 13:01:40 -05:00
main.h	auto-sync	2016-01-26 13:01:40 -05:00
makelinks.bat	…
map_resize.cpp	…
map_resize.h	…
readme.txt	…
rules.mk	…
settings.h	…
test.mk	…
test_accel_enrichment.cpp	auto-sync	2016-03-15 22:03:43 -04:00
test_accel_enrichment.h	…
test_engine_math.cpp	…
test_engine_math.h	…
test_fuel_map.cpp	auto-sync	2016-02-14 13:02:00 -05:00
test_fuel_map.h	…
test_idle_controller.cpp	…
test_idle_controller.h	…
test_logic_expression.cpp	auto-sync	2016-03-02 22:02:37 -05:00
test_logic_expression.h	…
test_sensors.cpp	auto-sync	2016-02-04 14:01:38 -05:00
test_sensors.h	…
test_signal_executor.cpp	…
test_signal_executor.h	…
test_speed_density.cpp	…
test_speed_density.h	…
test_trigger_decoder.cpp	auto-sync	2016-02-27 23:03:34 -05:00
test_trigger_decoder.h	auto-sync	2016-01-26 22:03:19 -05:00
test_util.cpp	auto-sync	2016-03-10 00:04:40 -05:00
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 :)