rusefi_documentation/Dev-Quality-Control.md

Development Quality Control

We love our engines and we want them to live a long & happy life. That's why we have a three-tier quality assurance process:

• Continuous Integration: Unit testing with Github Actions with ASan
• built-in trigger signal simulation
• Simulator

For current coverage report see the coverage page

Hardware Continuous Integration

STM32F407G-DISC1

Since 2015 there is always a stm32f4 board listening for VCS updates running rusEFI hardware continues integration, "HW CI" for short.

Anyone can execute real hardware test suite by invoking. This command would detect rusEFI hardware automatically and invoke HwCiF4Discovery.java

java -jar rusefi_console.jar functional_test

The following jumper wires are used to test some subsystems as realistically as possible:

• PD1 <=> PC6
• PD2 <=> PA5

Proteus F4

See c309174fdb/java_console/autotest/src/main/java/com/rusefi/proteus/ProteusAnalogTest.java (L22)

On setting new MXLinux runners

https://github.com/rusefi/rusefi/settings/actions/runners use hw-ci-f4-discovery or hw-ci-proteus-f7 group name while adding runner.

sudo mx-boot-options to set systemd as default

ufw allow 22

https://docs.github.com/en/actions/hosting-your-own-runners/managing-self-hosted-runners/configuring-the-self-hosted-runner-application-as-a-service

https://elinux.org/Accessing_Devices_without_Sudo

sudo useradd -G plugdev USERNAME

echo 'ATTRS{idProduct}=="374b", ATTRS{idVendor}=="0483", MODE="666", GROUP="plugdev"' > /etc/udev/rules.d/10-my-openocd.rules

sudo udevadm trigger