fome-fw/unit_tests
Matthew Kennedy 85304392dd two throttles one thread (#1806)
* two throttles one thread

* look at all this RAM!
2020-09-18 13:47:49 -04:00
..
googletest@dcc92d0ab6
test_basic_math
tests two throttles one thread (#1806) 2020-09-18 13:47:49 -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 better unit test logging 2020-07-20 13:38:33 -04:00
engine_test_helper.cpp DebounceButton A/C switch (#1782) 2020-09-10 22:16:20 -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 auto-sync 2015-07-10 09:01:56 -04:00
logicdata.cpp
logicdata.h
logicdata_sandbox.cpp
main.cpp
map_resize.cpp
map_resize.h
mocks.h two throttles one thread (#1806) 2020-09-18 13:47:49 -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 less hacky testing implementation 2020-09-03 22:52:29 -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