mirror of https://github.com/rusefi/rusefi-1.git
ee41d37c08
|
||
|---|---|---|
| .. | ||
| googletest@dea0216d0c | ||
| test_basic_math | ||
| tests | ||
| .cproject | ||
| .gitignore | ||
| .project | ||
| Makefile | ||
| adc_inputs.h | ||
| afm2mapConverter.cpp | ||
| afm2mapConverter.h | ||
| boards.cpp | ||
| boards.h | ||
| compile.bat | ||
| efifeatures.h | ||
| engine_test_helper.cpp | ||
| engine_test_helper.h | ||
| global.h | ||
| global_execution_queue.cpp | ||
| global_execution_queue.h | ||
| globalaccess.h | ||
| gmock-all.cpp | ||
| gtest-all.cpp | ||
| jenkins.sh | ||
| main.cpp | ||
| map_resize.cpp | ||
| map_resize.h | ||
| os_access.h | ||
| readme.txt | ||
| rules.mk | ||
| settings.h | ||
| test.mk | ||
| triggers.txt | ||
| unit_test_framework.cpp | ||
| unit_test_framework.h | ||
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 :)