rusefi-1/unit_tests
rusefi ace9a28a1b do we have a major defect? 2017-04-11 14:34:30 -04:00
..
test_basic_math do we have a major defect? 2017-04-11 14:34:30 -04:00
.cproject simple Makefile project for unit_tests 2017-04-10 14:20:11 -04:00
.project
Makefile fixing CI 2017-04-07 13:30:50 -04: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 auto-sync 2017-02-17 01:01:43 -05:00
efifeatures.h standard header 2017-03-05 21:59:00 -05:00
engine_test_helper.cpp reducing variable name conflict 2017-03-28 18:59:42 -04:00
engine_test_helper.h auto-sync 2016-12-18 12:03:48 -05:00
global.h comments 2017-03-07 01:43:58 -05:00
jenkins.sh
junction.exe
main.cpp removing dead files 2017-04-07 13:50:55 -04:00
main.h better method name & docs 2017-03-04 09:13:08 -05: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 removing dead file 2017-04-07 13:38:03 -04:00
test_accel_enrichment.cpp auto-sync 2016-11-30 21:06:24 -05:00
test_accel_enrichment.h
test_engine_math.cpp
test_engine_math.h
test_fuel_map.cpp refactoring - extracting sensors storage class 2017-03-07 02:24:57 -05:00
test_fuel_map.h
test_idle_controller.cpp #4 starting to remove old idle implementation 2017-03-23 20:35:45 -04:00
test_idle_controller.h #4 starting to remove old idle implementation 2017-03-23 20:35:45 -04:00
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 reducing variable name conflict 2017-03-28 18:59:42 -04: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 :)