rusefi-1/unit_tests
rusefillc 07a905b1fe revering functional part of
Etb function cfg, try again #1860
try again from #1831
2020-10-08 17:09:00 -04:00
..
googletest@dcc92d0ab6
test_basic_math
tests revering functional part of 2020-10-08 17:09:00 -04:00
.cproject
.gitignore
.project
Makefile The Big Refactoring of 2019: folder structure #723 2020-08-02 20:55:27 -04:00
adc_inputs.h
boards.cpp
boards.h
ci_gcov.sh
compile.bat
compile.sh
efifeatures.h
engine_test_helper.cpp nicer parameter name 2020-09-21 08:57:56 -04:00
engine_test_helper.h DebounceButton A/C switch (#1782) 2020-09-10 22:16:20 -04:00
global.h
global_execution_queue.cpp expose the problem 2020-07-31 14:41:29 -07:00
global_execution_queue.h expose the problem 2020-07-31 14:41:29 -07:00
globalaccess.h
gmock-all.cpp
gtest-all.cpp
jenkins.sh
logicdata.cpp
logicdata.h
logicdata_sandbox.cpp
main.cpp
map_resize.cpp
map_resize.h
mocks.h replace ETB index with function enum (#1807) 2020-09-28 16:33:07 -04:00
os_access.h
readme.md
rules.mk
run_clean_gcov.sh
run_gcov.bat
run_logicdata_sandbox.bat
test.mk
unit_test_framework.cpp relax a little 2020-07-31 19:02:48 -07:00
unit_test_framework.h Etb function cfg, try again (#1860) 2020-10-08 14:12:03 -04:00

readme.md

In this folder we have rusEfi unit tests using https://github.com/google/googletest

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.

  1. Run 'make' to build desktop binary.
  2. Execute rusefi_test binary on your PC/Mac, it's expected to say SUCCESS and not fail :) Googletest will also print results summary.

Code Coverage Report