rusefi
/
rusefi-1
mirror of https://github.com/rusefi/rusefi-1.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
rusefi-1/unit_tests
History
rusefi 05181cd837 migrating to googletest 2019-01-14 17:44:03 -05:00
..
googletest@542e057c6c googletest 2019-01-03 18:37:12 -05:00
test_basic_math migrating to googletest 2019-01-14 15:37:05 -05:00
tests migrating to googletest 2019-01-14 17:44:03 -05: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 auto-sync 2015-07-10 09:01:56 -04:00
Makefile windows unit tests are now 64 bit 2019-01-12 14:31:55 -05:00
adc_inputs.h auto-sync 2017-01-03 06:05:22 -05:00
afm2mapConverter.cpp #538 2018-01-21 16:11:39 -05:00
afm2mapConverter.h #538 2018-01-21 00:12:50 -05:00
boards.cpp Question: something strange trigger errors #662 2019-01-12 15:32:40 -05:00
boards.h Question: something strange trigger errors #662 2019-01-12 15:32:40 -05:00
compile.bat ooooops I forgot about Jenkins settings! 2019-01-12 21:15:05 -05:00
efifeatures.h #655 clean-up 2019-01-09 00:25:45 -05:00
engine_test_helper.cpp docs 2019-01-14 12:59:57 -05:00
engine_test_helper.h docs 2019-01-14 11:36:46 -05:00
global.h new unit test 2019-01-11 19:08:15 -05:00
global_execution_queue.cpp The Big Refactoring of 2019: scheduler should not be global #655 2019-01-09 20:06:41 -05:00
global_execution_queue.h The Big Refactoring of 2019: scheduler should not be global #655 2019-01-09 20:06:41 -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 auto-sync 2015-07-10 09:01:56 -04:00
main.cpp migrating to googletest 2019-01-14 15:31:56 -05: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
readme.txt docs 2017-04-21 19:05:02 -04:00
rules.mk auto-sync 2015-07-10 09:01:56 -04:00
settings.h auto-sync 2015-07-10 09:01:56 -04:00
test.mk BUG: phase sensor validation attending #659 2019-01-13 22:52:22 -05:00
triggers.txt different precision with different bitness in compiler? 2019-01-12 15:03:41 -05:00
unit_test_framework.cpp migrating to googletest 2019-01-14 15:37:05 -05:00
unit_test_framework.h migrating to googletest 2019-01-14 17:44:03 -05: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 :)