History

Matthew Kennedy d8898a4665 cherry picks from #385		2024-03-13 00:56:53 -07:00
..
chibios-mock	…
googletest@b10fad38c4	update googletest, because why not	2023-11-17 00:20:21 -08:00
test_basic_math	fix tests for no shadowing	2023-11-01 17:31:08 -07:00
tests	correct big buffer move assignment/constructor behavior	2024-02-29 00:09:57 +00:00
.cproject	enabling parallel compilation from Eclipse	2019-01-04 00:18:08 -05:00
.gitignore	…
.project	auto-sync	2015-07-10 09:01:56 -04:00
Makefile	gen config with make (#363 )	2024-02-22 10:58:03 -08:00
adc_inputs.h	…
boards.cpp	…
boards.h	happy new year	2020-01-08 00:02:40 -05:00
ci_gcov.sh	…
efifeatures.h	ancient history dead histogram	2023-04-11 17:02:56 -07:00
engine_test_helper.cpp	these lines just did NOTHING?	2023-11-01 17:16:14 -07:00
engine_test_helper.h	…
global.h	cherry picks from #385	2024-03-13 00:56:53 -07:00
global_execution_queue.cpp	dead code, reduce typedefs (#4566 )	2022-09-11 16:08:11 -04:00
global_execution_queue.h	…
global_mocks.cpp	…
gmock-all.cpp	…
gtest-all.cpp	…
logicdata.cpp	fix tests for no shadowing	2023-11-01 17:31:08 -07:00
logicdata.h	…
logicdata_csv_reader.cpp	fix tests for no shadowing	2023-11-01 17:31:08 -07:00
logicdata_csv_reader.h	fix tests for no shadowing	2023-11-01 17:31:08 -07:00
logicdata_sandbox.cpp	…
main.cpp	…
map_resize.cpp	…
map_resize.h	…
mocks.cpp	…
mocks.h	Add cranking taper duration multiplier based on CLT (#370 )	2024-02-25 17:36:30 -08:00
readme.md	rename test binary	2023-04-11 16:26:15 -07:00
rules.mk	…
run_clean_gcov.sh	rename test binary	2023-04-11 16:26:15 -07:00
run_gcov.bat	…
run_logicdata_sandbox.bat	…
run_sharded_tests.sh	scripts should fail harder when they fail	2024-03-07 22:17:37 -08:00
svnversion.h	…
test.mk	…
triggers.txt	triggers.txt	2023-09-14 13:59:18 -07:00
unit_test_framework.cpp	…
unit_test_framework.h	…
unit_test_rules.mk	unit tests get a board name for now	2024-03-07 22:59:47 -08:00

readme.md

TL, DR: just follow tests folder as examples.

Run 'make' to build desktop binary.
Execute fome_test binary on your PC/Mac, it's expected to say SUCCESS and not fail :) Googletest will also print results summary.
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

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.