rusefi/unit_tests
rusefillc fb66699cd8 odd fire angles are not right during cranking
#6281

only:docs
2024-03-25 10:09:02 -04:00
..
chibios-mock unit_test: ThreadReference mock 2024-03-11 16:54:58 -04:00
googletest@c231e6f5b1 fresh googletest 2024-03-15 21:32:42 -06:00
test-framework bosch quick start decoding issue or else #6281 2024-03-24 01:15:35 -04:00
test_basic_math confusing Map3D API fix #6139 2024-03-04 17:58:24 -05:00
tests odd fire angles are not right during cranking 2024-03-25 10:09:02 -04:00
.cproject dead warningEnabled global variable (#5636) 2023-10-24 18:55:29 -04:00
.gitignore
.project
Makefile only: JNI for test coverage fix #3965 2024-03-06 10:46:50 -05:00
adc_inputs.h
boards.cpp
boards.h
ci_gcov.sh
clean_compile.bat
clean_compile.sh
efifeatures.h AlternatorController unit-tests 2023-11-10 17:13:50 -05:00
global.h better placement for executor include 2024-02-16 21:16:11 -04:00
global_mocks.cpp only:returning useful mocks 2023-11-01 19:08:27 -04:00
gmock-all.cpp only:spelling 2023-06-15 14:53:38 -04:00
gtest-all.cpp make unit tests compatible with latest googletest #2064 2023-06-15 16:29:28 -04:00
logicdata.cpp only:trying to help mac compiler 2024-03-23 08:48:02 -04:00
logicdata.h avoid UB in tests 2024-03-23 07:54:27 -04:00
main.cpp only:reducing unit test logging 2024-02-21 17:31:02 -05:00
mocks.cpp
mocks.h only:making boost constraints more obvious, also running boost in simulator 2023-10-19 21:06:09 -04:00
readme.md only:docs 2024-02-21 17:30:41 -05:00
rules.mk fix unit tests cleaning 2024-02-24 19:37:15 -05:00
run_clean_gcov.sh
run_gcov.bat
run_logicdata_sandbox.bat
run_sharded_tests.sh Fix trigger error indicator (#4185) 2022-05-19 09:43:42 -04:00
svnversion.h
test.mk improving unit_tests folder structure 2023-08-08 20:11:24 -04:00
triggers.txt Trigger wheel definitions 2024-03-22 17:51:29 +00:00
unit_test_rules.mk unit test mk line is not needed twice 2024-03-16 17:41:52 -06:00

readme.md

See https://github.com/rusefi/rusefi/wiki/Dev-Quality-Control

TL, DR: just follow tests folder as examples. gcc/makefile/gtest

  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.
  3. To run only one test uncomment and modify main.cpp line ::testing::GTEST_FLAG(filter)

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.