a2nr
/
velxio
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

test(coverage): accept raspberry-pi-4 and raspberry-pi-5 as uncovered 

Pi 4 and Pi 5 were added to the BoardKind union in db5e3a8 ("feat(pi3
phase 3.1+3.2): Pi 3/4/5 family via PI_CONFIGS") but no gallery example
ships for them — same situation as Pi 3, which is already accepted.
All three boot a full Linux image under QEMU on the backend; there is
no in-browser canvas demo to register.
This commit is contained in:
David Montero 2026-05-18 15:56:54 +02:00
parent 5f378ed411
commit 683a7f31e6
1 changed files with 4 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
frontend/src/__tests__/board-kinds-coverage.test.ts
View File

@ -41,9 +41,11 @@ const ALL_EXAMPLES: ExampleProject[] = [
* coverage gap visible at code-review time.
*/
const ACCEPTED_UNCOVERED: ReadonlySet<BoardKind> = new Set([
// Pi 3B runs on the backend (QEMU ARM64) — no in-browser canvas
// example because it boots a full Linux image.
// Pi 3/4/5 run on the backend (QEMU ARM64) — no in-browser canvas
// example because they boot a full Linux image.
'raspberry-pi-3',
'raspberry-pi-4',
'raspberry-pi-5',
// ESP32 Xtensa LX6 variants — all share the same QEMU backend as
// the primary `esp32` boardKind (which IS covered). Adding a