fome-fw/unit_tests
GitHub build-unit-tests Action 8e954c89cf Trigger wheel definitions 2021-01-19 00:14:52 +00:00
..
googletest@dcc92d0ab6
test_basic_math templated interpolate2d (#2221) 2021-01-11 08:00:15 -05:00
tests Revert "Save more space in the angle cache (#2228)" 2021-01-18 18:53:00 -05:00
.cproject
.gitignore Trigger action (#2070) 2020-12-12 21:36:41 -05:00
.project
Makefile Partition configs by board type (#2106) 2020-12-22 21:54:40 -05:00
adc_inputs.h Adc isAdcChannelValid helper (#2188) 2021-01-05 16:02:20 -05:00
boards.cpp
boards.h
ci_gcov.sh
compile.bat
compile.sh
efifeatures.h Partition configs by board type (#2106) 2020-12-22 21:54:40 -05:00
engine_test_helper.cpp Fix gpio reinit race condition (#2098) 2020-12-18 17:18:12 -05:00
engine_test_helper.h
global.h clean up some includes (#2227) 2021-01-16 09:45:45 -05:00
global_execution_queue.cpp
global_execution_queue.h
globalaccess.h
gmock-all.cpp
gtest-all.cpp
jenkins.sh
logicdata.cpp
logicdata.h
logicdata_sandbox.cpp
main.cpp generate triggers.txt from parametric test (#2186) 2021-01-05 17:58:34 -05:00
map_resize.cpp
map_resize.h
mocks.h
os_access.h
readme.md
rules.mk
run_clean_gcov.sh
run_gcov.bat
run_logicdata_sandbox.bat
svnversion.h
test.mk
triggers.txt Trigger wheel definitions 2021-01-19 00:14:52 +00:00
unit_test_framework.cpp
unit_test_framework.h

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