custom-board-bundle-sample-.../unit_tests
Matthew Kennedy bc15e0826d
CLT consumer: fsio (#1302)
* idle

* CLT test prep

* idle target

* header

* air interpolate

* ancient comment

* fuel cut

* fuel cut, idle tests

* cleanup

* fsio test help
2020-04-15 16:20:45 -04:00
..
googletest@dea0216d0c
test_basic_math code style 2020-04-01 21:32:21 -04:00
tests CLT consumer: fsio (#1302) 2020-04-15 16:20:45 -04:00
.cproject
.gitignore
.project
Makefile fix warnings (#1282) 2020-04-12 09:39:14 -04:00
adc_inputs.h code style 2020-04-01 21:32:21 -04:00
afm2mapConverter.cpp
afm2mapConverter.h code style 2020-04-01 21:32:21 -04:00
boards.cpp
boards.h
compile.bat
efifeatures.h smart gpio clean-up 2020-04-06 14:13:29 -04:00
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 code style 2020-04-01 21:32:21 -04:00
globalaccess.h
gmock-all.cpp
gtest-all.cpp
jenkins.sh
main.cpp code style 2020-04-01 21:32:21 -04:00
map_resize.cpp
map_resize.h code style 2020-04-01 21:32:21 -04:00
os_access.h code style 2020-04-01 21:32:21 -04:00
readme.md
rules.mk
run_clean_gcov.sh
run_gcov.bat
run_gcov.sh
test.mk
triggers.txt
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