spaxel/firmware/test
jedarden b86cb670a8
Some checks are pending
CI Benchmark - Fusion Loop Timing / Fusion Loop Timing Benchmark (push) Waiting to run
test: print neutral RUN marker on direct setjmp==0 path
The direct branch of main()'s per-test setjmp loop — taken when a test
runs normally without longjmping back — now prints "RUN: <name>" instead
of "PASS: <name>". This is the same neutral marker family child 1
(bf-52k2) chose for the else branch ("RUN: <name> (assertion failed)"),
so a passing test prints "RUN: <name>" and a failing test prints
"RUN: <name> (assertion failed)".

After this child, NEITHER branch emits PASS/FAIL; each test emits exactly
one neutral line. The internal passed++ counter is unchanged — it feeds
the run summary ("N passed, M failed of T"), not the per-test output, so
it is not an "observable label". g_failure_count accounting is likewise
untouched.

Child 2 of 4 for bf-38e9 (split-child 2 of bf-53ut).

Co-Authored-By: Claude <noreply@anthropic.com>
2026-07-03 14:01:29 -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: print neutral RUN marker on direct setjmp==0 path 2026-07-03 14:01:29 -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