rusefi-1/unit_tests
Matthew Kennedy e2974cfeda
short term fuel trim: part 2 (#1405)
* add tooltip

* add other direction to deadband

* add impl

* test partitioning

* makefile

* wrong comment

* fix include
2020-05-07 08:52:32 -04:00
..
googletest@dcc92d0ab6 Closed loop controller base & ETB testing (#1322) 2020-04-19 17:18:47 -04:00
test_basic_math ETB testing: output, position clamping (#1333) 2020-04-20 13:52:20 -04:00
tests short term fuel trim: part 2 (#1405) 2020-05-07 08:52:32 -04:00
.cproject
.gitignore TT_RENIX_66_2_2_2 2020-04-19 14:54:02 -04:00
.project
Makefile
adc_inputs.h
afm2mapConverter.cpp
afm2mapConverter.h
boards.cpp
boards.h
compile.bat
efifeatures.h
engine_test_helper.cpp CLT consumer: fsio (#1302) 2020-04-15 16:20:45 -04:00
engine_test_helper.h CLT consumer: fsio (#1302) 2020-04-15 16:20:45 -04:00
global.h CLT consumer: fsio (#1302) 2020-04-15 16:20:45 -04:00
global_execution_queue.cpp
global_execution_queue.h
globalaccess.h
gmock-all.cpp
gtest-all.cpp
jenkins.sh
main.cpp consistency 2020-04-18 22:46:22 -04:00
map_resize.cpp
map_resize.h
mocks.h TPS Auto Calibration with ETB (#1382) 2020-04-28 19:31:41 -04:00
os_access.h
readme.md
rules.mk
run_clean_gcov.sh
run_gcov.bat
run_gcov.sh
test.mk
unit_test_framework.cpp consistency 2020-04-18 22:46:22 -04:00
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