fome-fw/unit_tests
Matthew Kennedy c1941f3a49 (void) -> () (#3550)
* static functions with (void)

* more

* Revert "more"

This reverts commit 246e53441f935451437df186ac92d7df26b62fb6.

* s

Co-authored-by: Matthew Kennedy <makenne@microsoft.com>
2021-11-15 13:02:34 +01:00
..
chibios-mock trigger signal debug pins - logic level output #2959 2021-07-15 00:50:29 -04:00
googletest@dcc92d0ab6
test_basic_math support autoscale on table axes (#3452) 2021-11-03 19:53:26 -04:00
tests (void) -> () (#3550) 2021-11-15 13:02:34 +01:00
.cproject
.gitignore
.project
Makefile better pch usage and gmock constructors (#3426) 2021-10-30 20:31:09 -04:00
adc_inputs.h
boards.cpp
boards.h
ci_gcov.sh Use SSH for remaining workflows (#3407) 2021-10-25 08:22:31 -04:00
clean_compile.bat
clean_compile.sh
efifeatures.h
engine_test_helper.cpp less macro, more c++ (#3549) 2021-11-15 12:44:40 +01:00
engine_test_helper.h
global.h WITH_ENGINE_TEST_HELPER_BOARD_CALLBACK 2021-11-08 12:27:02 -05:00
global_execution_queue.cpp
global_execution_queue.h add cancel to scheduler (#3201) 2021-08-27 11:30:06 +03:00
global_mocks.cpp
globalaccess.h
gmock-all.cpp
gtest-all.cpp
jenkins.sh
logicdata.cpp
logicdata.h
logicdata_csv_reader.cpp
logicdata_csv_reader.h
logicdata_sandbox.cpp
main.cpp
map_resize.cpp
map_resize.h
mocks.cpp test TS writes (#3515) 2021-11-10 07:29:40 -05:00
mocks.h test TS writes (#3515) 2021-11-10 07:29:40 -05:00
os_access.h
readme.md
rules.mk unit test build times (#3489) 2021-11-06 21:20:24 -04:00
run_clean_gcov.sh
run_gcov.bat
run_logicdata_sandbox.bat
run_sharded_tests.sh
svnversion.h
test.mk
triggers.txt Trigger wheel definitions 2021-11-14 23:14:04 +00:00
unit_test_framework.cpp
unit_test_framework.h
unit_test_rules.mk Compile each project's PCH to a separate file to reduce developer friction. (#3505) 2021-11-08 15:52:58 -05:00

readme.md

TL, DR: just follow tests folder as examples

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

See also https://github.com/rusefi/rusefi/wiki/Build-Server-and-Automation

Triggers Images

Trigger images generation is still a two-step manual process:

Step 1: Invoke unit_tests. One of the unit_tests artifacts is triggers.txt

Step 2: Once we have triggers.txt updated by unit_tests we can invoke firmware/gen_trigger_images.bat in order to generate actual trigger images.