rusefi-1/unit_tests
rusefi 14199080b1
Trigger rabbit hole (#682)
fix #681

* this did not work right

* progress: spinning is detected sooner now

* and now things are much better?

* and now reducing RAM usage
2019-01-24 21:12:55 -05:00
..
googletest@542e057c6c
test_basic_math
tests Trigger rabbit hole (#682) 2019-01-24 21:12:55 -05:00
.cproject
.gitignore
.project
Makefile trying ideas about testability 2019-01-17 00:24:41 -05:00
adc_inputs.h
afm2mapConverter.cpp
afm2mapConverter.h
boards.cpp
boards.h
compile.bat
efifeatures.h
engine_test_helper.cpp unit tests framework fix 2019-01-22 23:09:34 -05:00
engine_test_helper.h testing API improvement (?) 2019-01-21 22:34:17 -05:00
global.h refactoring: reducing header tree hell 2019-01-20 23:44:05 -05:00
global_execution_queue.cpp
global_execution_queue.h
gmock-all.cpp
gtest-all.cpp
jenkins.sh
main.cpp trying ideas about testability 2019-01-17 00:24:41 -05:00
map_resize.cpp
map_resize.h
readme.txt
rules.mk
settings.h
test.mk trying ideas about testability 2019-01-17 00:24:41 -05:00
triggers.txt
unit_test_framework.cpp migrating to googletest 2019-01-14 23:40:13 -05:00
unit_test_framework.h migrating to googletest 2019-01-14 23:40:13 -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 :)