rusefi
/
rusefi
mirror of https://github.com/rusefi/rusefi.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
rusefi/unit_tests
History
rusefi f8a3d900dc migrating to google test 2019-07-25 00:28:04 -04:00
..
googletest@dea0216d0c fresh googletest 2019-06-02 14:56:32 -04:00
test_basic_math Template-ize bin/value length for interpolation (#878) 2019-07-09 21:16:36 +03:00
tests migrating to google test 2019-07-25 00:28:04 -04:00
.cproject enabling parallel compilation from Eclipse 2019-01-04 00:18:08 -05:00
.gitignore trigger image progress 2018-02-28 23:31:58 -05:00
.project
…
Makefile reviving unit tests 2019-07-06 21:00:34 -04:00
adc_inputs.h
…
afm2mapConverter.cpp Template-ize bin/value length for interpolation (#878) 2019-07-09 21:16:36 +03:00
afm2mapConverter.h #538 2018-01-21 00:12:50 -05:00
boards.cpp #699 2019-02-28 21:09:31 -05:00
boards.h #699 2019-02-28 21:09:31 -05:00
compile.bat ooooops I forgot about Jenkins settings! 2019-01-12 21:15:05 -05:00
efifeatures.h More compatibility for ADC_inputs, etc. (#716) 2019-03-28 22:46:10 -04:00
engine_test_helper.cpp reducing code duplication with unit tests 2019-05-12 20:24:35 -04:00
engine_test_helper.h BUG: phase sensor validation attending - detect missing CAM signal #659 2019-05-10 21:56:33 -04:00
global.h refactoring: reducing code duplication 2019-02-23 12:33:49 -05:00
global_execution_queue.cpp random cleanup 2019-04-15 19:24:46 -04:00
global_execution_queue.h random cleanup 2019-04-15 19:24:46 -04:00
globalaccess.h #657 2019-01-28 02:59:14 -05:00
gmock-all.cpp #35 first unit test with a mock! 2019-01-08 01:20:18 -05:00
gtest-all.cpp googletest 2019-01-03 20:14:23 -05:00
jenkins.sh
…
main.cpp FIRMWARE_ID 2019-07-13 14:08:08 -04:00
map_resize.cpp migrating to googletest 2019-01-14 15:45:35 -05:00
map_resize.h auto-sync 2017-01-03 14:05:36 -05:00
os_access.h Refactoring: OS access should be explicit #867 2019-07-03 21:48:04 -04:00
readme.txt docs 2017-04-21 19:05:02 -04:00
rules.mk
…
settings.h
…
test.mk MK clean-up 2019-06-15 16:43:30 -04:00
triggers.txt CBR600 trigger progress 2019-07-23 19:22:40 -04:00
unit_test_framework.cpp migrating to google test 2019-07-25 00:28:04 -04:00
unit_test_framework.h migrating to google test 2019-07-25 00:28:04 -04:00

readme.txt 

In this folder we have a naive test suite.

I am not sure what is the best approach to tests in C (someone can educate me), but my approach is:

Unit tests are not aware of ChibiOS or ARM or else, they are just plain C/C++ which you build for your desktop, not your MCU.

Run 'make' to build desktop binary & run it on your PC/Mac, it's expected to say SUCCESS and not fail :)