fome-fw/unit_tests
rusefi 95d3368b0f refactoring: all events are now validated in relation to current timestamp 2019-10-07 23:02:47 -04:00
..
googletest@dea0216d0c
test_basic_math
tests refactoring: all events are now validated in relation to current timestamp 2019-10-07 23:02:47 -04:00
.cproject
.gitignore
.project
Makefile Sensors: composition >> inheritance (#953) 2019-09-24 21:11:41 -04:00
adc_inputs.h ETB target is using integer values #945 2019-09-22 09:56:06 -04:00
afm2mapConverter.cpp
afm2mapConverter.h
boards.cpp ETB target is using integer values #945 2019-09-22 17:58:27 -04:00
boards.h ETB target is using integer values #945 2019-09-22 16:52:22 -04:00
compile.bat
efifeatures.h ETB target is using integer values #945 2019-09-22 16:52:22 -04:00
engine_test_helper.cpp refactoring: all events are now validated in relation to current timestamp 2019-10-07 23:02:47 -04:00
engine_test_helper.h refactoring: all events are now validated in relation to current timestamp 2019-10-07 23:02:47 -04:00
global.h ETB target is using integer values #945 2019-09-22 09:56:06 -04:00
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.md
rules.mk
run_clean_gcov.sh
run_gcov.bat
run_gcov.sh
settings.h
test.mk
triggers.txt
unit_test_framework.cpp
unit_test_framework.h ETB target is using integer values #945 2019-09-22 09:56:06 -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