spaxel/firmware/test
jedarden d299306cb0 test: drop stale PASS/FAIL reference in host-harness loop comment
The per-test setjmp loop's doc comment still said it lands back in the
loop "to print PASS/FAIL and advance" — but child 1 (bf-52k2) and
child 2 (bf-344n) already replaced both branches' outcome labels with
the neutral RUN marker family ("RUN: <name>" / "RUN: <name>
(assertion failed)"). The comment now contradicts the code, so align
it with the "neutral marker line" phrasing already used lower in the
same block. No code change; gcc -std=c11 -Wall -Wextra still clean.

Co-Authored-By: Claude <noreply@anthropic.com>
Bead-Id: bf-344n
2026-07-03 14:55:47 -04:00
..
.gitignore test: land firmware host-test build scaffolding (Makefile, .gitignore, sanity) 2026-07-03 11:56:34 -04:00
Makefile test: land firmware host-test build scaffolding (Makefile, .gitignore, sanity) 2026-07-03 11:56:34 -04:00
test_csi_frame.c test: add firmware host tests for nvs/csi/serial_prov + wire gcc harness into CI 2026-07-03 13:21:26 -04:00
test_nvs_migration.c test: add firmware host tests for nvs/csi/serial_prov + wire gcc harness into CI 2026-07-03 13:21:26 -04:00
test_runner.c test: drop stale PASS/FAIL reference in host-harness loop comment 2026-07-03 14:55:47 -04:00
test_runner.h test: add firmware host harness header — TEST() macro + assert macros 2026-07-03 06:57:58 -04:00
test_sanity.c test: land firmware host-test build scaffolding (Makefile, .gitignore, sanity) 2026-07-03 11:56:34 -04:00
test_serial_prov.c test: add firmware host tests for nvs/csi/serial_prov + wire gcc harness into CI 2026-07-03 13:21:26 -04:00