mirror of https://github.com/FOME-Tech/fome-fw.git
761efd862c
* use engine module callbacks * happy tests * happy small-can-board * interact with map avg via module * simplify map avg init * tweaks * omit module to disable it instead! * unnecessary guard * minor cleanups * unnecessary branch - lookups for these tables are fine at 0 rpm * oop |
||
|---|---|---|
| .. | ||
| chibios-mock | ||
| googletest@b10fad38c4 | ||
| test_basic_math | ||
| tests | ||
| .cproject | ||
| .gitignore | ||
| .project | ||
| Makefile | ||
| adc_inputs.h | ||
| boards.cpp | ||
| boards.h | ||
| ci_gcov.sh | ||
| efifeatures.h | ||
| engine_test_helper.cpp | ||
| engine_test_helper.h | ||
| global.h | ||
| global_execution_queue.cpp | ||
| global_execution_queue.h | ||
| global_mocks.cpp | ||
| gmock-all.cpp | ||
| gtest-all.cpp | ||
| logicdata.cpp | ||
| logicdata.h | ||
| logicdata_csv_reader.cpp | ||
| logicdata_csv_reader.h | ||
| logicdata_sandbox.cpp | ||
| main.cpp | ||
| mocks.cpp | ||
| mocks.h | ||
| 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 | ||
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.
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.