Validation
Validation is how a claim gets evidence. ROHI distinguishes the levels and never lets one stand in for another: compilation is not hardware validation.
| Level | How | Where |
|---|---|---|
| Host tests | cargo test, in-memory devices and mocked buses, no hardware | Host testing |
| Target builds | cargo check-esp32c3, cargo check-esp32c6 and the firmware builds in CI | Targets and features |
| Resource budget | measured flash, RAM and stack | Resource budget |
| Hardware | a recorded run on a physical board | Hardware testing |
Validating on hardware
- Build and flash the firmware or an example for your board (Quick start).
- Follow the procedure and checklist of Hardware testing for the capability you are checking.
- Record the result: device and revision, firmware revision, procedure, outcome and logs, in a report you can link.
- Add the result to the support matrix: change
hardware_verificationand attach the report ashw-reportevidence. The validator rejectsverifiedorfailedwithout it.
Sharing results
A hardware report can be a pull request that adds the report and updates the matrix, or an issue with the same content.
A failure is as valuable as a success and is recorded as failed.