forked from rusefi/rusefi
-
Notifications
You must be signed in to change notification settings - Fork 0
Dev Quality Control
David Holdeman edited this page Jan 24, 2022
·
3 revisions
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](https://github.com/rusefi/rusefi/actions? query=workflow%3A%22Unit+Test+CI%22) see unit_tests
- built-in trigger signal simulation
- Simulator
For current coverage report see the coverage page
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 broken link
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
- How to search the Wiki
- Quick Start
- How to ask questions
- Support
- How to create a TunerStudio project
- HOWTOs and FAQs
- rusEFI project overview
- rusEFI Online
- rusEFI virtual simulator
- Fueling
- Multispark
- Cranking
- Electronic Throttle
- Knock Sensing
- Variable Valve Timing
- Lua Scripting
- GDI
- Digital Dash
- rusEFI Hardware Overview
- Wiring & Connectivity Overview
- rusEFI Assembly Completeness Chart
- Kit Instructions
- Hellen Miata 90-95
- Hellen Miata 96-97
- Hellen Miata 99-00
- Hellen Miata 01-05 VVT
- MREAdapter55: from Lada to e30
- Frankenso MazdaMiataNA6 PnP
- Creating a PnP PCB