fome-fw/unit_tests
Matthew Kennedy 044e575af6 Map3D considered harmful #421 2024-05-03 22:55:18 -07:00
..
chibios-mock Simpler thread controller (#4327) 2022-08-02 01:16:13 +03:00
googletest@b10fad38c4
test_basic_math
tests Map3D considered harmful #421 2024-05-03 22:55:18 -07:00
.cproject
.gitignore
.project
Makefile
adc_inputs.h we often mean inline when we say static 2024-03-28 18:20:40 -07:00
boards.cpp
boards.h
ci_gcov.sh
efifeatures.h
engine_test_helper.cpp setTimeNowUs(): replace global fiddling with a functino call 2024-04-27 01:59:38 -07:00
engine_test_helper.h no need for getTimeNowUs on ETH 2024-04-27 01:48:02 -07:00
global.h setTimeNowUs(): replace global fiddling with a functino call 2024-04-27 01:59:38 -07:00
global_execution_queue.cpp unit test global cleanup 2024-04-26 02:02:49 -07:00
global_execution_queue.h
global_mocks.cpp unit test time is actually stored in ticks 2024-04-27 02:04:25 -07:00
gmock-all.cpp
gtest-all.cpp
logicdata.cpp maybe fix mac 2024-03-23 13:13:04 -07:00
logicdata.h avoid UB in tests 2024-03-22 12:07:58 -07:00
logicdata_csv_reader.cpp
logicdata_csv_reader.h
logicdata_sandbox.cpp
main.cpp
map_resize.cpp
map_resize.h
mocks.cpp
mocks.h Map3D considered harmful #421 2024-05-03 22:55:18 -07:00
readme.md
rules.mk
run_clean_gcov.sh
run_gcov.bat
run_logicdata_sandbox.bat
run_sharded_tests.sh
svnversion.h
test.mk
triggers.txt
unit_test_framework.cpp
unit_test_framework.h
unit_test_rules.mk cleanup & explicit Builds on windows are not supported by FOME (#392) 2024-03-19 12:54:41 -07:00

readme.md

TL, DR: just follow tests folder as examples.

  1. Run 'make' to build desktop binary.
  2. Execute fome_test binary on your PC/Mac, it's expected to say SUCCESS and not fail :) Googletest will also print results summary.
  3. To run only one test, run like this: build/fome_test --gtest_filter=MyTestName

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.

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.