Your firmware has no tests because CMake fought you, not because you didn't want them
The real reason firmware projects skip unit tests isn't willpower — it's a day of CMake archaeology to get a host build and a cross-compiled target build to coexist. Here is that build, the HAL boundary that makes hardware-touching code testable, and why host-runnable tests are the precondition for an AI agent doing useful work on firmware at all.